chore(scripts): stop generating content for archived versions - #4671
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
There was a problem hiding this comment.
Should we also mention to add the archiving version back to scripts if it was removed? These steps kind of cover both archiving an existing version and an already removed version.
brandyscarney
approved these changes
Aug 27, 2026
brandyscarney
left a comment
brandyscarney
left a comment
Member
There was a problem hiding this comment.
Looks good, just noted one place we could add a note.
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.
Issue URL: N/A
What is the current behavior?
scripts/native.mjsandscripts/cli.mjswrite generated content to v6 and v7 on every build. Both are archived and served from frozen Vercel deployments, so that's 140 files per build that nothing reads.The archiving checklist in CONTRIBUTING doesn't mention the scripts, so the lists go stale on each release.
What is the new behavior?
docs/(current) andversioned_docs/version-v8(the one older version still inversions.json)Does this introduce a breaking change?
Other information
The generated files are git-ignored, so nothing was committed and nothing is removed from the repo. The frozen deployments already contain their own baked copies.
Verified by backdating the v6 and v7 output, then re-running both scripts: those directories stayed untouched while
docs/andversion-v8were rewritten.