chore: delete the vestigial VERSION file#104
Merged
Merged
Conversation
It said 3.24.1 while the package was 3.33.0 — a second, wrong source of truth for the version. Nothing reads it: no reference anywhere in src/, scripts/, .github/, install.sh or docs, and it isn't in package.json `files`, so it was never published to npm either. Deleting it cannot affect the package. History shows it was part of the release ritual through v3.24.1 (2026-06-01) and then quietly dropped — every release since (3.25 → 3.33) left it behind. package.json is the real version; this file only existed to mislead the next person who grepped for it.
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.
VERSIONsaid 3.24.1 while the package was 3.33.0 — a second, wrong source of truth.Safe to delete — verified, not assumed:
src/,scripts/,.github/,install.sh, or docspackage.jsonfiles(["dist","assets","README.md","LICENSE"]), so it was never published to npm — confirmed against the real3.33.0tarball (0 matches). Removing it cannot affect the package.git log -- VERSIONshows it was part of the release ritual through v3.24.1 (2026-06-01), then quietly dropped — every release since (3.25 → 3.33) left it behind.package.jsonis the real version; this file only existed to mislead the next person who grepped for it.