Skip to content

release: grant security-events write to lint job - #594

Merged
4og merged 1 commit into
mainfrom
fix/release-lint-security-events-permission
Sep 17, 2026
Merged

4og merged 1 commit into
mainfrom
fix/release-lint-security-events-permission

Conversation

@4og

@4og 4og commented Sep 17, 2026

Copy link
Copy Markdown
Member

Problem

The manually dispatched Release v0.2.13 workflow failed at startup (no jobs were created): https://github.com/eclipse-score/baselibs/actions/runs/35204834600

GitHub Actions reported:

Error calling workflow 'eclipse-score/baselibs/.github/workflows/lint.yml@e3354f5a8feab5f03a90492f0d33d4ee21ff9228'.
The workflow is requesting 'security-events: write', but is only allowed 'security-events: none'.

Root cause

.github/workflows/lint.yml was updated to request security-events: write (for SARIF upload to code scanning), but its caller, .github/workflows/release.yml, only grants contents: read and actions: write at the workflow level and does not override permissions for the lint job. Reusable workflows cannot elevate permissions above what the caller grants, so GitHub rejects the entire run before any job is scheduled.

Fix

Grant security-events: write (along with contents: read and actions: write) scoped to just the lint job in release.yml, matching the existing pattern already used for the build-qnx job. No other release job's permissions change.

Verification

  • Confirmed via gh run view and the run's HTML error message that this is the exact permission mismatch causing the startup_failure.
  • Ran bazel run //tools:format.fix -- .github/workflows/release.yml; no additional formatting changes were needed.

The release workflow's lint job calls .github/workflows/lint.yml,
which requests security-events: write to upload SARIF to code
scanning. The release workflow only granted contents: read and
actions: write at the workflow level, so GitHub Actions rejected the
run at startup with:

  Error calling workflow '.../lint.yml@...'. The workflow is
  requesting 'security-events: write', but is only allowed
  'security-events: none'.

Reusable workflows cannot elevate permissions beyond what the caller
grants, so this failed before any job was scheduled (see run
https://github.com/eclipse-score/baselibs/actions/runs/35204834600).

Grant the missing permission scoped to just the lint job, matching
the existing pattern used for the build-qnx job, so no other release
job gains elevated privileges.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-project-automation github-project-automation Bot moved this from In Progress to On Hold in BAS - Baselibs FT Sep 17, 2026
@fbaeuerle
fbaeuerle enabled auto-merge September 17, 2026 12:49
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-594: https://eclipse-score.github.io/baselibs/pr-594/

@4og
4og disabled auto-merge September 17, 2026 13:25
@4og
4og merged commit e7ddf3b into main Sep 17, 2026
24 of 27 checks passed
@4og
4og deleted the fix/release-lint-security-events-permission branch September 17, 2026 13:25
@github-project-automation github-project-automation Bot moved this from On Hold to Done in BAS - Baselibs FT Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI related changes

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants