You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why this PR appeared today after a 6-week gap, and one risk before you merge.
The Release workflow had been failing on every push to main since at least 2026-08-07. Root cause: release PR #52 (release 0.7.0, merged 2026-07-11) still carried the autorelease: pending label. v0.7.0 was minted by hand during the documented 2026-07-11 token incident, so the label was never flipped to tagged — release-please therefore re-attempted "create release for #52" on every push, hit Resource not accessible by integration on releases#create, and failed the run before it could ever open a new Release PR.
Net effect: 136 commits sat unreleased and mise use -g github:cerebral-work/linearctl has been frozen at 0.7.0 for a month.
Fix applied: flipped #52 to autorelease: tagged — a metadata correction asserting something already true (the v0.7.0 tag and GitHub Release both exist), fully reversible, no release created. Then re-drove release-please via the workflow's documented bare-dispatch lever. The run went green for the first time since before 2026-08-07, producing this PR.
Risk to know before merging — I did not fix this and the green run is not evidence I did: merging this PR drives releases#create, which is the exact call that was refused in July. The workflow job already grants contents: write + pull-requests: write, so the grants are not obviously the problem, and the header notes the July refusal happened with "grants identical to prior green runs; user-token creates fine." If it re-fires, the documented recovery applies: mint the release by hand, then workflow_dispatch with tag=vX.Y.Z to compile/attest/upload the binaries.
Releases are operator-gated, so this PR is left open for the operator. Filed from the linearctl lane.
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
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.
🤖 I have created a release beep boop
0.8.0 (2026-08-18)
Features
Bug Fixes
Code Refactoring
Documentation
This PR was generated with Release Please. See documentation.