deps: Update dependency commit-and-tag-version to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
commit-and-tag-version	^12.7.3 → ^13.1.0

---

Release Notes

absolute-version/commit-and-tag-version (commit-and-tag-version)

v13.1.0

Compare Source

Features

• support ESM configuration files (#​306) (9e0e5ab)

v13.0.0

Compare Source

⚠ BREAKING CHANGES

• Update all conventional-changelog dependencies to their modern version. There are a few breaking changes that will affect users with custom presets, please see MIGRATION.md. This also raises the node minimum to node 22.
• This package is now pure ESM. CLI uses should be unaffected. This raises the minimum engine to 20.19, and anyone using require will need to require('commit-and-tag-version').default

deps

• Update all conventional-changelog dependencies to their modern version. There are a few breaking changes that will affect users with custom presets, please see MIGRATION.md. This also raises the node minimum to node 22. (c2d26bf)

Bug Fixes

• maven: preserve comments in pom.xml (#​294) (cbb6010)

Code Refactoring

• This package is now pure ESM. CLI uses should be unaffected. This raises the minimum engine to 20.19, and anyone using require will need to require('commit-and-tag-version').default (89ba82e)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "after 12pm on Friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 7 workspace projects
? Verifying lockfile against supply-chain policies (884 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 0, added 0
Progress: resolved 40, reused 0, downloaded 0, added 0
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 0, added 0
Progress: resolved 50, reused 0, downloaded 0, added 0
Progress: resolved 100, reused 0, downloaded 0, added 0
Progress: resolved 246, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (884 entries in 11.6s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  eslint@10.8.0 was published at 2026-07-24T20:15:20.693Z, within the minimumReleaseAge cutoff (2026-07-24T01:48:48.330Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.