deps: bump vitest from 5.0.2 to 5.0.3 in the vitest group - #17
Closed
dependabot[bot] wants to merge 10 commits into
Closed
dependabot[bot] wants to merge 10 commits into
dependabot[bot] wants to merge 10 commits into
Conversation
Bumps @cldmv/fix-headers to 2.1.4 and re-runs npm run fix:headers. 37 files' headers were restamped.
Drop forceAuthorUpdate from the shared config. With it on (together with useGpgSignerAuthor), anyone who ran fix-headers in an extending repository replaced every file's @author with their own name. @author records who created the file, so fix-headers' default of keeping it is the right house setting; a repository can still turn the option on for a one-off migration. Refs #15
Keep the option in the shared config as false instead of omitting it, so the decision is visible and overrides anything earlier in an extends chain.
Bumps the vitest group with 1 update: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `vitest` from 5.0.2 to 5.0.3 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.3/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vitest ... Signed-off-by: dependabot[bot] <support@github.com>
![cldmv-bot[bot]](https://avatars.githubusercontent.com/in/1910694?s=60&v=4){kind=small}
cldmv-bot
Bot
added
the
type: dependencies
cldmv-bot
Bot
dismissed
their stale review
October 4, 2026 06:36
The merge-base changed after approval.
Shinrai
approved these changes
Oct 4, 2026
Contributor
|
@dependabot rebase |
Author
|
Looks like vitest is no longer updatable, so this is no longer needed. |
auto-merge was automatically disabled
October 4, 2026 06:59
Pull request was closed
dependabot
Bot
deleted the
dependabot/npm_and_yarn/next/vitest-3fdc1deb3f
branch
October 4, 2026 06:59
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.
Bumps the vitest group with 1 update: vitest.
Updates
vitestfrom 5.0.2 to 5.0.3Release notes
Sourced from vitest's releases.
Commits
33cadeachore: release v5.0.3 (#11409)346d389fix(vm): don't reuse scripts across vite environments (#11395)f6c9a49fix(deps): pinwhy-is-node-runningto3.2.1to avoid users running into `...062c75dchore: fix standalone docs build, update exports maps (#11394)caf2887fix(vm): do not optimize deps from index.html (fix #11329) (#11360)50312ebfix(pool): preserve unique pool ids whengroupOrderis set (#11392)7c36748fix(browser): ignore page crash while cancelling (#11386)92ba7fcfix: scope cache key generators to projects (fix #11281) (#11301)38f9885fix(cache): revalidate imports of cached modules (#11381)b24585ffix: don't retry whentest.failsexpectedly failed (#11219)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions