Pin fixed next release action - #6981
Conversation
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Added
.github/workflows/release-queue-input-diagnostic.yml, a temporary workflow that runs the unmergednext-release-actiondiagnostic path on GitHub-hosted runners to compare raw and parsedeligible_branchesinput.
The workflow follows the claimed safety constraints: it triggers only on pull_request, grants only contents: read, passes the default ${{ github.token }} rather than the bot token, and invokes a pinned SHA of next-release-action with NEXT_RELEASE_ACTION_DIAGNOSTIC: "true" so the action exits before constructing GitHub or git services.
@v0 or keep the SHA fresh with Dependabot | View workflow run | Using Kimi K2 (free via Pullfrog for OSS) | 𝕏
|
Diagnostic completed successfully. The runner exposed Result: https://github.com/Effect-TS/effect/actions/runs/30914706194/job/92009757386 The production fix is in Effect-TS/next-release-action#3. |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
-
Updated the pinned
Effect-TS/next-release-actionSHA fromadcadc4to424506bso the diagnostic workflow exercises the action PR'sLayer.provideMergefix, which exposes the constant-caseConfigProviderto the main effect's input reads. -
Confirmed the rest of the workflow remains unchanged:
pull_requesttrigger only, read-onlycontents: readpermission, default${{ github.token }}, quotedeligible_branches, andNEXT_RELEASE_ACTION_DIAGNOSTIC: "true". -
Verified via the upstream PR description that the new SHA was produced by the
vp check,vp test --run, andvp packverification steps.
@v0 or keep the SHA fresh with Dependabot | View workflow run | Using Kimi K2 (free via Pullfrog for OSS) | 𝕏
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
This run reviewed the new commit since the prior pullfrog review.
- Removed the temporary
.github/workflows/release-queue-input-diagnostic.ymlworkflow that was used to exercise the unmerged action fix. - Updated the pinned
Effect-TS/next-release-actionSHA in.github/workflows/release-queue.ymlfrom73b52b4034f708dbed94db384459ca5ba9437979to0901387026995718742a42e0f6bf7743d0d83c2f, which corresponds to the merged upstream PR #3 (Expose the config provider to the action).
@v0 or keep the SHA fresh with Dependabot | View workflow run | Using Kimi K2 (free via Pullfrog for OSS) | 𝕏
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|

Purpose
Pin the release queue workflow to the merged
next-release-actionconfig-provider fix. This allows the action to read the configuredv4/next-minorandv4/next-majorbranches instead of using its fallback branch names.Action fix: Effect-TS/next-release-action#3
Verification
pnpm lintgit diff --check