Skip to content

fix: create releases after artifacts - #113

Draft
iancleary wants to merge 1 commit into
mainfrom
release-ordering-111
Draft

fix: create releases after artifacts#113
iancleary wants to merge 1 commit into
mainfrom
release-ordering-111

Conversation

@iancleary

Copy link
Copy Markdown
Owner

Summary

  • keep just cut-release as the release entrypoint, but dispatch and wait for the checked-in release workflow instead of creating the GitHub release locally
  • run contributor checks and every supported platform build before assembling and verifying artifacts and attestations
  • make gh release create the workflow's final step so failed prerequisites leave no release tag or published release
  • pin attestation verification to the immutable commit targeted by the release tag
  • allow a clean, already-versioned main to resume an unpublished release after a failed workflow
  • update the managed cut-release and create-release-process skills, repo guidance, and release documentation

Root cause

The release workflow was triggered by the published release event. That required the tag and GitHub release to exist before platform builds, artifact assembly, and attestation verification had run.

Verification

  • just ci
  • cargo check
  • just release-process-check
  • shell syntax checks for the release, installer, and regression-check scripts
  • YAML parse check for .github/workflows/release-artifacts.yml

The structured autoreview helper was also attempted, but its required TruffleHog dependency is not installed in the local environment.

Closes #111

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.

Release process is backwards

1 participant