release: v2.2.1 - bump @cldmv/configs to 1.2.4 - #132
Merged
Merged
Conversation
Contributor
Author
🔒 Dependency Review
|
Contributor
Author
📦 Bundle size unchanged
📊 Generated by |
Shinrai
approved these changes
Oct 5, 2026
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
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.
@cldmv/fix-headers v2.2.1 Changelog
Release Date: October 2026
Release Type: Patch
Branch:
release/2.2.1Overview
Version 2.2.1 moves the repository's own development setup to
@cldmv/configs1.2.4. Nothing the package ships changed:dist/,bin/, the generated types and the runtime dependencyignoreare exactly as in v2.2.0. The published package differs only in theversionfield and in the@cldmv/configsrange recorded in itsdevDependencies.The shared config is what the repository's own
npm run fix:headersextends, so the bump changes how fix-headers stamps its own source files. Version 1.2.4 turns offforceAuthorUpdateandforceLastModifiedAuthorUpdate, which were both on in 1.2.0. With v2.2.0 of the tool, that means@Authoris never rewritten, and@Last modified bychanges only when a file's content was edited. The run that accompanied the bump scanned 109 files and changed none.🔧 Dependencies
@cldmv/configs^1.2.0→^1.2.4(#131), dev dependency. The lockfile moves from 1.2.0 to 1.2.4, and that is the only dependency entry that changed. Between those versions the sharedfix-headers.jsonswitchedforceAuthorUpdate(1.2.3) andforceLastModifiedAuthorUpdate(1.2.4) fromtruetofalse. It is used bynpm run fix:headersand by nothing that ships.📚 Documentation
Upgrade notes
@cldmv/configs'fix-headers.jsonshould use@cldmv/configs1.2.4 or later together with@cldmv/fix-headers2.2.0 or later. On older versions of the tool, the forced author settings that 1.2.4 turns off behave differently.👥 Contributors
Avg: 100.0% ·
674426c· Node lts/*Co-authored-by: Shinrai Shinrai@users.noreply.github.com