Bump Deno to 2.9.7

[dahlia]

mise.toml pins the toolchain, and it still pointed at Deno 2.9.5. This moves the pin to 2.9.7 and updates the places that duplicate it to keep the versions consistent: the setup-deno action and the three Compose files that run Fedify in a container (examples/monitoring/compose.yaml, test/smoke/mastodon/docker-compose.yml, and test/smoke/sharkey/docker-compose.yml). The Deno version is not recorded in deno.lock, so no lockfile needed regenerating.

[netlify]

✅ Deploy Preview for fedify-json-schema canceled.

Name	Link
🔨 Latest commit	16fc709
🔍 Latest deploy log	https://app.netlify.com/projects/fedify-json-schema/deploys/6abd1f2f5b63ac0007a33e19

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: fec3fa2a-32f4-46a3-984f-b8a023a54850

📥 Commits

Reviewing files that changed from the base of the PR and between 4fe1b8c and 16fc709.

📒 Files selected for processing (5)

• .github/actions/setup-deno/action.yaml
• examples/monitoring/compose.yaml
• mise.toml
• test/smoke/mastodon/docker-compose.yml
• test/smoke/sharkey/docker-compose.yml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

---

📝 Walkthrough

Walkthrough

The Deno version changes from 2.9.5 to 2.9.7 in the setup action, tool configuration, monitoring example, and smoke-test container configurations.

Changes

Deno Version Alignment

Layer / File(s)	Summary
Update Deno version references .github/actions/setup-deno/action.yaml, mise.toml, examples/monitoring/compose.yaml, test/smoke/mastodon/docker-compose.yml, test/smoke/sharkey/docker-compose.yml	These configurations now use Deno 2.9.7 instead of 2.9.5.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 16fc7

The listed Deno configurations are aligned at 2.9.7. No actionable merge risk is identified.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 16fc7

The changes only advance Deno version pins. Declared permissions, network exposure, mounts, and certificate configuration remain unchanged. No introduced security concern was identified, but runtime-release behavior and deployment compatibility were not established.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• observed — The replaced container runtime executes the monitoring sample with environment and network access, and the smoke-test harnesses with environment, network, read, and write access plus workspace mounts. These capabilities predate this PR; the substitution does not expand their declared scope.

Trust Boundaries and Controls

• observed — Both smoke-test harnesses retain STRICT_MODE, the existing DENO_CERT path, and read-only certificate mounts. The PR changes neither these declarations nor the configured Deno permission flags; their effective enforcement by the upgraded runtime remains unverified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating Deno from 2.9.5 to 2.9.7.
Description check	✅ Passed	The description accurately explains the Deno version update and identifies the affected configuration and Compose files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.