docs: correct the "no tags" claim and record the release blocker - #38
Merged
Merged
Conversation
Two corrections to notes I wrote during Phase 58 prep. The repo does have tags — v1.0.0 through v2.7.0, with matching GitHub releases, the most recent published 2026-03-22. My earlier note said there were none; that came from reading a shallow clone that had not fetched tags, not from the remote. What is true, and was the actual point, is that the version sat at 2.7.0 through both the v3.0 and v3.1 milestones: those shipped no release. Second, this session cannot cut the v3.1.0 release. `git push origin v3.1.0` returns HTTP 403 through the agent git proxy, and dispatching release.yml returns "Resource not accessible by integration". Recorded as a maintainer action with the reason, rather than left as an unexplained unchecked box. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014nSJ2c7F9mpmRCxfTAi214
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
2 participants
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.
Two corrections to notes I wrote during Phase 58 prep. Planning docs only, no code.
I was wrong about tags
I wrote in
.planning/STATE.md(and in #37's description) that the repo has no tags. It does:v1.0.0throughv2.7.0, with matching GitHub releases, the most recent published 2026-03-22.The error came from reading a shallow clone that had not fetched tags and treating the empty output as the truth about the remote — the same shape of mistake this milestone exists to stamp out, so it gets corrected in the record rather than quietly dropped.
What was true, and was the actual point of the version bump, is that
workspace.package.versionsat at2.7.0through both the v3.0 and v3.1 milestones: neither shipped a release.This session cannot cut the release
Recorded with the reason instead of left as an unexplained unchecked box. Both paths are blocked by permissions, verified:
git push origin v3.1.0RPC failed; HTTP 403through the agent git proxyPOST /actions/workflows/release.yml/dispatches403 Resource not accessible by integrationBranch pushes work fine (this PR is one), so it is specifically tag refs and
actions: writethat are out of reach.The tag needs a maintainer. Either works:
git tag -a v3.1.0 983c42b -m "Release v3.1.0 — Make It True" git push origin v3.1.0or run the Release workflow via Actions → Release → Run workflow with version
3.1.0, which creates and pushes the tag itself.983c42bis the commit CI validated — the squash merge of #37.🤖 Generated with Claude Code
https://claude.ai/code/session_014nSJ2c7F9mpmRCxfTAi214
Generated by Claude Code