chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • "before 8am on the first day of the month"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[github-actions]

Preview Worker deployed: https://karinto-pr-74.toiroakr.workers.dev

curl -X POST --data-binary @workflow.yml https://karinto-pr-74.toiroakr.workers.dev

Add the regression-test label to re-run the dark-launch
replay against the latest commit.

_{Auto-cleaned when this PR closes.}

[github-actions]

Dark-launch comparison

Replayed 200 captures against https://karinto-pr-74.toiroakr.workers.dev.

	count
Matched	180
Ignored (expected diff)	20
Unexpected diff	0

Ignored diffs

• 5c65d2828de3 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 5eca30b1b0cf — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 607b1facd7cd — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 01c09dd40510 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 7a04c9d40b4f — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• c33981f70f7b — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 7012981211d2 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• bff22a068453 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 2f939f5eaf37 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 3da071916a3c — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• d8a5f590e9ec — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 1e5f424bf6ec — via expression-syntax-stray-brace-fix: PR feat: honour zizmor.yml config and fix linter parity divergences #62 stops flagging a stray }} as an expression-syntax error: a literal {{ }} template (e.g. docker/metadata-action's pattern={{version}}) is not a GitHub expression, only an unterminated ${{ is. Prod still serves the pre-fix worker, so captures carry the spurious expression syntax error: stray }} finding; replaying against the fixed worker drops it. `onlyInReplayed` must be empty (the fix only deletes a false positive, never adds findings). Some captures lose the stray-`}}` finding alongside other already-merged-but-unshipped removals on the same response: PR #55's single-quoted-string-literal `unknown-context-or-function` artifacts, and the already-shipped `unknown runner label `ubuntu-slim drop (current prod and the PR worker agree it should not fire; only the older snapshot still carries it). Each existing single-purpose rule requires every moving diagnostic to be its own category, so a capture mixing the stray-}} removal with those is matched by none. This rule suppresses exactly that: it fires only when a stray-}} removal is present, sets it (and the ubuntu-slim runner-label drop) aside, and requires the residual to be fully explained by PR fix: ignore single-quoted string literals in unknown-context scan #55's string-literal fix (delegated, so that rule stays the source of truth). A genuine regression — any added finding, or a removed finding outside this set — is still surfaced. Self-expiring: delete once feat: honour zizmor.yml config and fix linter parity divergences #62/fix: ignore single-quoted string literals in unknown-context scan #55 ship and prod captures roll over (~30 days post-release).
• 9602acf81b73 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• a74b22401969 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 7667ebe57134 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• 33e312f84700 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• b5b78ae382f2 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• ab8bd821c8aa — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• c9351a9831de — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.
• faec2affdd01 — via promote-zizmor-planned-rules: PR feat(rules): promote zizmor Planned rules to Implemented (parity 0/0) #14 promotes every Planned zizmor rule to Implemented (plus actionlint:yaml-anchor-issues) and broadens several already-Implemented rules. When the PR worker replays a request that was captured in prod before this PR shipped, the replayed response may add new findings, drop superseded ones, or rewrite severity/message of existing ones — all attributable to the rules listed below. This rule suppresses such diffs as long as every added or removed diagnostic's rule is in that set.