Skip to content

Security/node2shell - #156

Merged
marcusosterberg merged 2 commits into
mainfrom
security/node2shell
Oct 24, 2026
Merged

marcusosterberg merged 2 commits into
mainfrom
security/node2shell

Conversation

@marcusosterberg

Copy link
Copy Markdown
Contributor

No description provided.

The repository's default workflow token has write access, so every job,
including the ones that only build and test, could push code, create
releases or edit issues. If a step or a third party action in such a job
is compromised, it gets the same access.

Each workflow without a permissions block now starts with
permissions: contents: read. Jobs that need to write get their own block:

- create-release.yml: contents: write
  (creates the tag and GitHub release)
- prep-release.yml: contents: write, pull-requests: write
  (peter-evans/create-pull-request pushes a branch and opens a PR)

Changed: create-release.yml, linux.yml, manual-start.yml, prep-release.yml
Create Release runs on every push to main that touches package.json.
When package.json does not hold the next version, NEW_VERSION stays
empty and the GitHub Release step fails. And when a push run and a
manual run overlap, both release the same version and the release notes
end up twice (seen in webperf_core 2026.10.2).

- the release and publish steps now run only when NEW_VERSION is set,
  and a step says why the rest was skipped
- runs are queued (concurrency group, no cancel), so a second run sees
  the new tag, computes the next version and publishes nothing
@marcusosterberg
marcusosterberg merged commit e193cbd into main Oct 24, 2026
1 check passed
@marcusosterberg
marcusosterberg deleted the security/node2shell branch October 24, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

⌂ Proxy