deps: restore the vitest and globals bumps lost in the next reset - #21
Merged
Merged
Conversation
#18 (@vitest/coverage-v8 5.0.3) and #19 (globals 17.13.0) merged into next two minutes after the v1.2.3 release merged and were wiped by the post-release reset of next (CLDMV/.github#360). Re-applied at latest, together with vitest 5.0.3 from #17.
cldmv-bot
Bot
added
the
type: dependencies
Shinrai
approved these changes
Oct 4, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 4, 2026
# @cldmv/configs v1.2.4 Changelog **Release Date**: October 2026 **Release Type**: Patch **Branch**: `release/1.2.4` --- ## Overview The shared `fix-headers.json` stops forcing `@Last modified by`. Until now every fix-headers run in an extending repository stamped whoever ran it as the last modifier of every file it touched, even when the only change was a header rewrite such as a new date format. With `forceLastModifiedAuthorUpdate` set to `false` and fix-headers 2.2.0, `@Last modified by` now records the last person who actually edited a file's content, while `@Last modified time` still moves whenever fix-headers rewrites a header. Together with `forceAuthorUpdate: false`, which shipped in v1.2.3, the shared config no longer rewrites anyone's authorship: `@Author` keeps the file's creator, and `@Last modified by` follows real edits. Extending repositories should upgrade to `@cldmv/fix-headers` 2.2.0 or later alongside this release. --- ## 🐛 Bug Fixes ### `@Last modified by` follows real edits ([#20](#20)) `forceLastModifiedAuthorUpdate` was `true`, so every run rewrote `@Last modified by` to the identity running fix-headers (the name on their signing key, or `git config user.name` without one) on every file it changed. A contributor who ran `npm run fix:headers` therefore became the last modifier of every restamped file, even files they never opened ([#15](#15)). The option is now `false`. From fix-headers 2.2.0 ([CLDMV/fix-headers#128](CLDMV/fix-headers#128)) the field changes only when a file's content, everything outside the header, differs from the last commit, or when the file is new: | What changed in a file | `@Last modified time` | `@Last modified by` | `@Author` | | ------------------------------------------------------------------- | --------------------- | ------------------------------ | --------- | | Nothing | unchanged | unchanged | unchanged | | Only the header (date format, epoch, `@Date`, spacing, filename, …) | updated | unchanged | unchanged | | Content edited, or a new file | updated | the person running fix-headers | unchanged | On fix-headers releases before 2.2.0 the same setting keeps the existing `@Last modified by` on every run, real edits included, so the upgrade matters. ## 🔧 Dependencies - `@cldmv/fix-headers` `^2.1.4` → `^2.2.0` ([#20](#20)), dev-only. The repository's own header pass ran under 2.2.0 and changed no files. - `vitest` and `@vitest/coverage-v8` `^5.0.2` → `^5.0.3`, and `globals` `^17.12.0` → `^17.13.0` ([#21](#21)), dev-only. The coverage and globals bumps first merged as [#18](#18) and [#19](#19), two minutes after the v1.2.3 release, and were lost when `next` was reset after that release ([CLDMV/.github#360](CLDMV/.github#360)). #21 re-applies them, together with the vitest bump from [#17](#17). ## 📚 Documentation - **NEW:** [docs/changelog/v1/v1.2.4.md](./v1.2.4.md) — this changelog. - README: the `fix-headers.json` table and notes explain both author settings, and the requirements now name fix-headers 2.2.0 as the version the author rules need. - [v1.2.3](./v1.2.3.md) changelog corrected: that release also shipped `forceAuthorUpdate: false`, which its notes left out. --- ## Upgrade notes - **Upgrade `@cldmv/fix-headers` to 2.2.0 or later** in every repository that extends this config. On older fix-headers, `@Last modified by` would no longer update even when a file is edited. - The first fix-headers run after upgrading leaves existing `@Last modified by` values alone and only changes them on files whose content was edited since the last commit. No repository-wide restamp of authors. <details> <summary>👥 Contributors</summary> - @Shinrai </details> --- <!-- coverage-start -->  | Metric | Coverage | |--------|----------| | Statements | 100.0% | | Branches | 100.0% | | Functions | 100.0% | | Lines | 100.0% | *Avg: **100.0%** · `117287f` · Node lts/** <!-- coverage-end --> <!-- co-authors --> Co-authored-by: Shinrai <Shinrai@users.noreply.github.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.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
No new features
🐛 Bug Fixes
No bug fixes
📦 Dependencies
🔧 Other Changes
No other changes
👥 Contributors