Version 6.9.4

[ildyria]

Summary by CodeRabbit

• New Release

  • Lychee v6.9.4 is now available with multiple updates and improvements

• Bug Fixes & Improvements

  • Resolved migration errors that blocked older-version upgrades
  • Various bug fixes and frontend enhancements

• Technical Updates

  • Release signing format changed to .sigstore.json

• Documentation

  • Added Code Signing guidance, release notes entry, notable changes, and new contributors list

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Adds release notes for v6.9.4 (Oct 29, 2025) documenting a change to release signing (.sigstore.json), migration fixes to prevent 500 errors, notable bug/test/frontend items, a contributors list and changelog link. Updates announcement component links and display text from v6.9.2 to v6.9.4.

Changes

Cohort / File(s)	Summary
Release Documentation docs/releases.md	Adds v6.9.4 entry: documents new signing output (.sigstore.json) replacing .asc, migration fixes preventing 500 errors for older-version migrations, notable changes list, code-signing doc pointer, new contributors list, and full changelog link.
UI Components src/components/widgets/Announcement.astro	Updates visible release links and anchor text from v6.9.2 to v6.9.4 (e.g., "Lychee 6.9.4 is now available!"). No logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify version strings are consistent between docs/releases.md and src/components/widgets/Announcement.astro.
• Check the .sigstore.json signing description and changelog link target for correctness.

Poem

🐰 I hopped through lines to find the news today,
New sigs in JSON, old asc tucked away,
Migrations patched so no errors leap,
Announcements cheer — a release to keep,
I nibble carrots and code, and then I say: hooray! 🎉

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 679d90c and 9f779cc.

📒 Files selected for processing (1)

• docs/releases.md (1 hunks)

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/releases.md (1)

33-92: Consider removing "WIP" from PR title.

The release notes appear complete and well-structured. If the release entry is finalized, consider updating the PR title from "Version 6.9.4 - WIP" to "Version 6.9.4" to reflect the ready-to-merge status.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 659f879 and 679d90c.

📒 Files selected for processing (2)

• docs/releases.md (1 hunks)
• src/components/widgets/Announcement.astro (1 hunks)

🔇 Additional comments (4)

src/components/widgets/Announcement.astro (2)

13-14: LGTM! Version references updated correctly.

The announcement banner has been properly updated to reference v6.9.4 with consistent href and display text.

---

17-17: Commented reference also updated for consistency.

Good practice to keep commented code synchronized with the current version, even if it's not actively displayed.

docs/releases.md (2)

45-84: Well-structured release notes.

The notable changes section is comprehensive and properly formatted with:

• Clear categorization (fix, klo, SE, new tags)
• Proper PR references
• Good use of blockquotes for additional context
• Helpful Code Signing documentation links

---

91-91: The changelog link is correct—v6.9.3 was never released.

Based on verification, v6.9.3 does not exist as a git tag and is not documented in releases.md. The link comparing v6.9.2 to v6.9.4 is therefore intentional and accurate, as it covers all released versions between those points.

Likely an incorrect or invalid review comment.