chore: remove stale releases/ dir + fix README build docs#36
Merged
Conversation
The releases/ folder (5.3M, frozen at v1.4.0, Feb 2024) is a leftover from the pre-CDN manual release flow. The current CI deploy.yml builds minified bundles and uploads straight to S3/CloudFront — it never writes here, so none of the v2.x builds were ever in it. README's "Building from source" section still described the old behavior (release.sh minifying + writing to releases/); release.sh now only tags, with the build happening in CI. Both corrected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
releases/folder (5.3M, frozen at v1.4.0 since Feb 2024). The current CI (deploy.yml) builds + uploads to S3/CloudFront and never writes here — no v2.x build was ever committed to it.releases/). release.sh now only tags; CI does the build.Risk
Only affects anyone still loading
kyte.jsfrom the raw GitHubreleases/stable/path instead of the CDN — believed to be nobody post-CDN-migration.🤖 Generated with Claude Code