Skip to content

fix: validate releases before publishing#52

Merged
Addono merged 1 commit intomainfrom
copilot/fix-release-validation-order
Mar 30, 2026
Merged

fix: validate releases before publishing#52
Addono merged 1 commit intomainfrom
copilot/fix-release-validation-order

Conversation

@Addono
Copy link
Copy Markdown
Owner

@Addono Addono commented Mar 30, 2026

Summary

  • move release-candidate validation into its own job before semantic-release runs
  • rebuild the CLI with the resolved release version before validation so versioned binary checks stay accurate
  • make the gh extension integration test compare against the installed checkout entrypoint instead of inferred release state

Validation

  • npm run lint
  • npm run format:check
  • npm run typecheck
  • npm run build
  • npm test
  • simulated release validation with GH_ATTACH_BUILD_VERSION=9.9.9

Move release candidate validation ahead of semantic-release and make the gh extension integration test assert against the installed checkout entrypoint instead of inferred release state.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Addono Addono merged commit dc6b449 into main Mar 30, 2026
9 checks passed
@Addono Addono deleted the copilot/fix-release-validation-order branch March 30, 2026 13:13
github-actions Bot pushed a commit that referenced this pull request Mar 30, 2026
## [1.5.5](v1.5.4...v1.5.5) (2026-03-30)

### Bug Fixes

* align release tests with computed build version ([#51](#51)) ([f2bd3d6](f2bd3d6))
* inject release version during binary build ([#50](#50)) ([6496db2](6496db2))
* validate releases before publishing ([#52](#52)) ([dc6b449](dc6b449))
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