fix(ci): initialize release state on the runner - #24
Merged
Merged
Conversation
jaysin586
added
enhancement
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.
Summary
The automatic release run after #23 was rejected before any job started because
runner.tempis unavailable in job-levelenv. InitializeRELEASE_STATEin the first runner step viaRUNNER_TEMPandGITHUB_ENV, retaining a path outside checkout isolated by run ID and attempt.Changes
Docs-kit owns the generator migration and CalVer template correction. Sync regression coverage proves existing hardened workflows migrate once and remain idempotent. The shared regression test executes the real initialization shell and verifies separate attempts use separate state paths. Existing release triggers, signing, registry authentication, and version-tagged actions are preserved.
Validation
Actionlint validates release and test workflows. Offline release tests pass on Node 22 and 24, including the new state-path regression. Existing package source checks, builds, and units passed in the preceding rollout; this correction changes no package source. Trunk and configured ESLint results are recorded in the rollout evidence; pre-existing hermetic ESLint installer limitations remain in keyed/render/purify. This PR carries
skip-publish. No live release was dispatched.Commits
cd74e65test(ci): import runner test environment explicitlye661cb2fix(ci): initialize release state on the runner