Repository navigation
ci(release): job names render on every branch — no needs in a name - #8
Merged
Merged
Conversation
GitHub does not evaluate `needs.*` in the name of a job it skips, so the jobs a branch does not run
showed as "Release ${{ needs.plan.outputs.tag }} on dev" and "Publish ${{ … }} to npm". Names use
the github context only, as library-publish's "Promote to ${{ github.ref_name }}" does; the version
is in each job's summary. No version bump: merging this releases nothing.
Co-Authored-By: Igor Lamos <igor@be.plus>
igorlamos
approved these changes
Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub does not evaluate
needs.*in the name of a job it skips. So on every Release run, the jobs that branch doesn't run showed asRelease ${{ needs.plan.outputs.tag }} on dev,Promote ${{ needs.plan.outputs.tag }} to …andPublish ${{ needs.plan.outputs.tag }} to npm.The names now use the github context only: Release on dev, Promote to ${{ github.ref_name }} (library-publish's form) and Publish to npm. The version is in each job's summary. One file changed (
.github/workflows/release.yml);npm run lintis clean.There's no version bump, so merging this into
devreleases nothing.