Conversation
Bumps the patch group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 26.1.1 to 26.1.2 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.1.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the patch group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 26.1.1 to 26.1.2 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will 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 version` will 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 </details>
cldmv-bot
Bot
added
! release → master
Contributor
Author
🔒 Dependency Review
|
The comparison header always stamped the current runner's git identity into @last modified by, so any machine whose git config user.name differed from what was recorded in existing headers flagged nearly every file as changed purely from an identity mismatch (1551/1565 in one observed run), even with zero real content change. Add extractHeaderLastModifiedIdentity() to parse the existing @last modified by line and preserve it in the comparison header unless the new forceLastModifiedAuthorUpdate option (--force-last-modified-author-update) is set, mirroring how @Author/@Email is already gated behind forceAuthorUpdate. Uses a dedicated flag rather than reusing forceAuthorUpdate since the two identities are independently meaningful to refresh. Closes #24
…ar dynamic The fixture header hard-coded a 2013-2026 copyright range, which mismatches the tool's default (current year) regardless of forceLastModifiedAuthorUpdate — the test would still report filesUpdated: 1 even if the force flag were a no-op, since the copyright-line mismatch alone forces the rewrite. Match the sibling preservation test's pattern of a dynamic current-year range so the force flag is the only reason the header changes. Addresses review comment on PR #25.
…fied identity forceLastModifiedAuthorUpdate only gated the comparison header used to decide whether a rewrite was needed. Once any other reason triggered needsUpdate (e.g. forceAuthorUpdate forcing createdBy to differ, or a malformed/missing @last modified time repair), the actual rewritten header unconditionally stamped the current runner's identity into @last modified by, bypassing the flag entirely and defeating the point of splitting it from forceAuthorUpdate. Apply the same preserve-unless-forced gate to the rewrite branch. @last modified time still always refreshes to now on any real rewrite — only the identity is gated. Addresses suppressed review finding on PR #25.
…Update The published TypeScript declarations were out of sync with the JSDoc source after adding forceLastModifiedAuthorUpdate to FixHeadersOptions, which would have produced type errors for TS consumers using the new flag. Regenerated via the project's own types:build script and kept only the line this PR's change touches — the regeneration also surfaced unrelated pre-existing drift in constants.d.mts, file-discovery.d.mts, and detectors/index.d.mts from other features already merged into next, which is out of scope here and left untouched. Addresses suppressed review finding on PR #25.
…ubset The previous commit manually stripped the gitignore-related lines out of the tsc-regenerated declarations to keep the diff scoped to this PR's own change. That was wrong: declaration output is fully deterministic from source, so trimming it just means the file ships already stale the moment this PR merges (missing gitignore, which this branch's own source already declares). Regenerate the full, untrimmed output via npm run types:build instead — picking up the pre-existing gitignore/root-anchor-ignores (74c34da) declaration drift alongside this PR's forceLastModifiedAuthorUpdate addition, so next isn't left stale in either direction regardless of merge order.
cldmv-bot
Bot
added
area: core
Shinrai
enabled auto-merge (squash)
August 9, 2026 06:10
Shinrai
approved these changes
Aug 9, 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
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
📦 Dependencies
🔧 Other Changes
👥 Contributors
Avg: 100.0% ·
4414ede· Node lts/*