Skip to content

fix(ci): prevent version-manifest job skip on tag push#10

Merged
matthew-on-git merged 1 commit intomainfrom
fix/version-manifest-job
Mar 9, 2026
Merged

fix(ci): prevent version-manifest job skip on tag push#10
matthew-on-git merged 1 commit intomainfrom
fix/version-manifest-job

Conversation

@matthew-on-git
Copy link
Contributor

Summary

  • Fix version-manifest job being silently skipped on tag pushes (e.g. v1.6.0)
  • Root cause: GitHub Actions transitive needs chain skip behavior — when auto-version is skipped (tag push trigger), downstream jobs inherit the skip even through build-and-push which uses always()
  • Fix: add always() with explicit needs.build-and-push.result == 'success' guard to the version-manifest job's if condition

Test plan

  • CI passes on this PR
  • Next tag push (manual or scheduled) triggers the version-manifest job
  • tool-versions.json is attached to the GitHub release

🤖 Generated with Claude Code

The version-manifest job was silently skipped on v1.6.0 due to GitHub
Actions transitive needs-chain behavior: when auto-version is skipped
(tag push), build-and-push uses always() to run anyway, but
version-manifest inherited the skip from the ancestor chain. Adding
always() with an explicit success check ensures the job runs whenever
build-and-push succeeds on a tag push.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@matthew-on-git matthew-on-git merged commit 4e49fb1 into main Mar 9, 2026
3 checks passed
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