chore(deps): update dependency @anolilab/semantic-release-pnpm to v8.1.16

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@anolilab/semantic-release-pnpm (source)	8.1.4 → 8.1.16

---

Release Notes

anolilab/semantic-release (@​anolilab/semantic-release-pnpm)

v8.1.16

Compare Source

Bug Fixes

• build: add @​visulima/pail devDependency to satisfy cerebro peer (a440c7d)
• lint: satisfy eslint-config v27 rules and make codecov upload non-blocking (da69704)

Dependencies

• @​anolilab/rc: upgraded to 4.0.4

v8.1.15

Compare Source

Bug Fixes

• semantic-release-pnpm: handle non-AggregateError in verify and skip re-publish (#​309) (6acb075)
• semantic-release-pnpm: soft-fail whoami for non-official registries (#​310) (b041d88)

Miscellaneous Chores

• deps: bump deps and upgrade to pnpm 11 (#​312) (100be77)

Dependencies

• @​anolilab/rc: upgraded to 4.0.3

v8.1.14

Compare Source

v8.1.13

Compare Source

v8.1.12

Compare Source

v8.1.11

Compare Source

v8.1.10

Compare Source

Miscellaneous Chores

• security: apply audit overrides (9607d56)

v8.1.9

Compare Source

v8.1.8

Compare Source

v8.1.7

Compare Source

v8.1.6

Compare Source

v8.1.5

Compare Source

Bug Fixes

• semantic-release-pnpm: align integration test with whoami error and add cache reset helper (fdfc677)
• semantic-release-pnpm: remove duplicate verifyAuthContextAgainstCustomRegistry function (dc64c44)
• semantic-release-pnpm: use npm pkg set on pnpm v10+ (c96d683)
• semantic-release-pnpm: use pnpm whoami for custom registry auth verification (afee204)

Tests

• semantic-release-pnpm: strengthen already-published regression test (6e84c11)
• semantic-release-pnpm: use distinct registry URL in whoami-failure test to avoid cache collision (5900697)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

[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

✓ Lockfile passes supply-chain policies (verified 18s ago)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 188, reused 0, downloaded 0, added 0
Progress: resolved 344, reused 0, downloaded 1, added 0
Progress: resolved 382, reused 0, downloaded 2, added 0
[ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for "nanoid@3.3.14" (possible package takeover)

This error happened while installing the dependencies of vite@8.0.8
 at postcss@8.5.15

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had staged publish, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.