chore(docs): archive v7 - #4679
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Issue URL: internal
What is the current behavior?
major-10.0still lists v7 as a live version inversions.json, so it builds and ships v7 docs. Main archived v7 in #4647 when it cut over to v9, but that change never reached this branch: it forked beforehand, andmajor-9.0, which would normally have carried it across, has since been deleted.This also blocks the next sync from main. The merge tooling derives which version was promoted by diffing the two
versions.jsonfiles, and expects exactly one result. Right now it gets two, v9 and v7, and stops before the merge can run:detect-versions: expected exactly one promoted version, got: v7 v9 . Resolve versions.json before merging.What is the new behavior?
v7 moves from
versions.jsontoversionsArchived.json, pointing at the same frozen deployment main uses. This branch now builds v10 as current, with v9 and v8 versioned, and links out to the archived v7, v6, and v5.The change mirrors #4647 exactly: two files, one line each. The
versioned_docs/version-v7tree and its sidebar stay on disk, since archiving removes a version from the build rather than deleting its files.With this in place the promoted version resolves to v9 alone, and the sync from main can proceed.
Does this introduce a breaking change?
Other information
Worth knowing for later: with
major-9.0gone,major-10.0is now two hops from main, and the merge tooling assumes a single hop. Anything main applied during the v9 cutover that this branch forked before will need the same treatment, as a companion commit rather than arriving through a sync.