[dependabot]

Bumps the development group with 2 updates: @re-cinq/eslint-plugin-re-lint and typescript-eslint.

Updates @re-cinq/eslint-plugin-re-lint from 1.8.0 to 1.10.0

Release notes

Sourced from @​re-cinq/eslint-plugin-re-lint's releases.

v1.10.0

• no-stale-spec-links reports a link it cannot repoint (unhealableLink), on the spec line with the reason, and no longer stays silent about it: a title no test carries or several carry, a cited line the branch rewrote, an anchor on a blank or closing line in a file the branch changed. A rotten anchor into a file the branch did not change is not reported. Before, such a link surfaced only as require-spec-link on the test, with a hint to run eslint --fix that could not help. A new error on specs that carried such links unnoticed. reportUnhealable: false turns the report off, for a repository that is still draining a queue of them.
• A label of the form validated by name:23, with or without backticks, and a label that opens with a stray bracket name no test, so the link is mapped through the diff hunks and is never reported as a missing title.
• require-spec-link's misanchoredLink says to run eslint --fix on the spec and to repoint by hand when no-stale-spec-links reports the link unhealable.
• A test declaration whose title sits below its opening line is read: a title prettier wrapped onto the next line (it(\n "title",) and an it.each whose table spans several lines. The declaration stays at its opening line, where require-spec-link counts the test from. Before, a titled link into such a test matched no declaration and was left alone, so it went stale without a word.

v1.9.0

• Every trailing parenthetical of a statement is read for its test links, not only the last. Done. ([validated by X](https://github.com/re-cinq/re-lint/blob/HEAD/a.test.ts#L10)) ([from plan](https://…)) used to drop the validated-by link silently, so the test read as unlinked wherever it pointed. Parentheticals before the last count only when they start with a link, so a prose aside earlier in the sentence is still not evidence.
• require-spec-link matches a link whose label names a test of the cited file ([validated by <title>], compared as re-lint-reanchor compares titles) to that test alone. Its anchor must land inside the test: one that drifted into a neighbour is reported on the named test (misanchoredLink) and no longer counts as linking the neighbour, so a shift reveals every unlinked test in one run instead of one per CI round. Labels that name no test of the file keep the old rule: any test the anchor lands in.
• no-stale-spec-links and re-lint-reanchor repoint such a link to the it() line of the test it names even in a file the branch did not change. A titled link that lands on no test there is still out of scope.

v1.8.1

• require-status-matches-coverage and require-statement-links resolve a document's test links against the git work tree the document sits in, not against the directory ESLint was run from. Run from a subdirectory, every repo-relative link used to miss, a document read as having no evidence, and a Draft status passed on a corpus whose links hold.

Changelog

Sourced from @​re-cinq/eslint-plugin-re-lint's changelog.

1.10.0

• no-stale-spec-links reports a link it cannot repoint (unhealableLink), on the spec line with the reason, and no longer stays silent about it: a title no test carries or several carry, a cited line the branch rewrote, an anchor on a blank or closing line in a file the branch changed. A rotten anchor into a file the branch did not change is not reported. Before, such a link surfaced only as require-spec-link on the test, with a hint to run eslint --fix that could not help. A new error on specs that carried such links unnoticed. reportUnhealable: false turns the report off, for a repository that is still draining a queue of them.
• A label of the form validated by name:23, with or without backticks, and a label that opens with a stray bracket name no test, so the link is mapped through the diff hunks and is never reported as a missing title.
• require-spec-link's misanchoredLink says to run eslint --fix on the spec and to repoint by hand when no-stale-spec-links reports the link unhealable.
• A test declaration whose title sits below its opening line is read: a title prettier wrapped onto the next line (it(\n "title",) and an it.each whose table spans several lines. The declaration stays at its opening line, where require-spec-link counts the test from. Before, a titled link into such a test matched no declaration and was left alone, so it went stale without a word.

1.9.0

• Every trailing parenthetical of a statement is read for its test links, not only the last. Done. ([validated by X](https://github.com/re-cinq/re-lint/blob/main/a.test.ts#L10)) ([from plan](https://…)) used to drop the validated-by link silently, so the test read as unlinked wherever it pointed. Parentheticals before the last count only when they start with a link, so a prose aside earlier in the sentence is still not evidence.
• require-spec-link matches a link whose label names a test of the cited file ([validated by <title>], compared as re-lint-reanchor compares titles) to that test alone. Its anchor must land inside the test: one that drifted into a neighbour is reported on the named test (misanchoredLink) and no longer counts as linking the neighbour, so a shift reveals every unlinked test in one run instead of one per CI round. Labels that name no test of the file keep the old rule: any test the anchor lands in.
• no-stale-spec-links and re-lint-reanchor repoint such a link to the it() line of the test it names even in a file the branch did not change. A titled link that lands on no test there is still out of scope.

1.8.1

• require-status-matches-coverage and require-statement-links resolve a document's test links against the git work tree the document sits in, not against the directory ESLint was run from. Run from a subdirectory, every repo-relative link used to miss, a document read as having no evidence, and a Draft status passed on a corpus whose links hold.

Commits

• 3600fa5 Report a spec link that cannot be repointed, on the spec line (#18)
• 4e8b897 Read a test title that sits below its opening line (#17)
• 9ea8e26 fix(rules): spec links in any trailing group count, and a titled link counts ...
• e898dae Ground test links against the work tree, not the directory ESLint ran from (#15)
• See full diff in compare view

Updates typescript-eslint from 8.72.0 to 8.72.1

Release notes

Sourced from typescript-eslint's releases.

v8.72.1

8.72.1 (2026-10-26)

🩹 Fixes

• eslint-plugin: [no-unnecessary-condition] false positives on unresolved conditional types (#13062)
• eslint-plugin: [no-unnecessary-type-assertion] bound recursive type traversal instead of catching stack overflows (#13039)
• typescript-estree: use one Program per tsconfig for the project service in single-run mode (#12988)

❤️ Thank You

• Evyatar Daud @​StyleShit
• Josh Ghoulberg 👻

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.72.1 (2026-10-26)

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Commits

• 4ad6b75 chore(release): publish 8.72.1
• 7757694 chore: cleanup typecheck & build and fix race condition (#13071)
• See full diff in compare view

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 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

[lore-agent]

Nothing blocks this PR from merging now. Lore updates this comment when the reason changes.

[github-actions]

Lore Spec Impact

Lore rejected the request (403) - the LORE_INGEST_TOKEN secret is missing, expired, or lacks the write scope.