Repository navigation
skill: Cut legacy docs branches at the release publish time, not the main tip - #2093
Draft
aditiabhang wants to merge 3 commits into
Draft
aditiabhang wants to merge 3 commits into
aditiabhang wants to merge 3 commits into
Conversation
…main tip During the 8.1 cutover, v8_0 was cut from the origin/main tip (fb50b82, #2090), which was merged six minutes after 8.1.0 was published and was marked "Merge after 8.1 releases". The skill told the agent to prefer the last commit on the release date or the tip, and never checked the actual release time. The cut-point section now uses the X.Y.0 publish time as a hard ceiling, lists docs PRs merged at or after it, flags PRs that may carry X.Y content (merge-after notes, post-branch-cut generated syncs, linked sourcegraph PRs on the X.Y.x branch), and requires the agent to propose the cut with evidence and wait for confirmation before creating or pushing the legacy branch. Amp-Thread-ID: https://ampcode.com/threads/T-01a140f9-34fa-726b-90c5-1608b2a7cc81
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
This comment has been minimized.
This comment has been minimized.
added 2 commits
October 15, 2026 19:33
This branch has not been deployed
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.
When 8.1 was released,
v8_0was cut from theorigin/maintipfb50b82b(#2090, "Merge after 8.1 releases", merged six minutes after 8.1.0 was published). 8.1 content landed in the 8.0 archive; it was re-cut fromddfe8c2. The skill told the agent to use the last commit on the release date or the tip, and never checked the release time. 7.7 had the same bug:v7_6includes #1843, merged 22 hours after 7.7.0 was published.Changes
X.Y.0publish time (GitHub releasepublished_at, changelog API as fallback) is a hard ceiling. Tag time is not used: it predates the public release by up to a day.X.Y.xbranch cut and the ceiling: "merge after" notes, generated-docs syncs after the branch cut, and docs PRs whose linked sourcegraph PR is onX.Y.x.Checked against history
5e5bb56,fb50b82brejected,ddfe8c2proposed (docs: Document displayName in declarative code host config #2078 links sourcegraph#16774 on8.1.x; 🤖 Sync generated docs from sourcegraph/sourcegraph #2071 is a post-cut sync).1249796; the actual cutf0addc6stays allowed.a543b1d; the actual cut4049388would be rejected.Test plan
Follow-ups
docs/legacy.mdxentries for new majors.hostname.split(".")[0]gives8, not8.0.