ci: disable husky hooks during semantic-release commit - #39
Merged
Conversation
@semantic-release/git commits CHANGELOG.md + package.json on release, which fired the pre-commit hook — gen:constants (needs `uv`), typecheck, and test — and failed on the Node-only release runner (`uv: not found`), aborting before publish. Set HUSKY=0 for the Release step so the release commit skips hooks.
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
1 participant
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.
The 2.0.0 release run (and the earlier Jun-27 run) failed at publish time:
@semantic-release/gitcommitsCHANGELOG.md+package.json, which fires the.husky/pre-commithook —gen:constants(cd agent && uv run python …),typecheck,test— and the Node-only release runner has nouv, so the commit fails (uv: not found) and semantic-release aborts before the npm publish. Net: 2.0.0 was computed correctly but never published (npm/CDN still 1.2.0).Fix: set
HUSKY: 0on the Release step. The release commit is[skip ci]and only bumps the changelog + version — it doesn't need the pre-commit suite (which already ran on the merged PRs).Merging this re-fires
release.yml, which recomputes 2.0.0 (thefeat!breaking commit is still in range since v1.2.0 was never tagged) and this time publishes@pydantic/ai-chat-ui@2.0.0to npm → jsdelivr.Pre-existing pipeline bug — surfaced while cutting 2.0.0 to unblock the pydantic-ai chat-UI integration.