Conversation
📝 WalkthroughWalkthroughAdds release notes for v6.8.1 in docs/releases.md with migration fix and minor features; standardizes “fix” to “fixes” across entries. Updates Announcement.astro to reference v6.8.1 in link and text. No code or API changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (6)
docs/releases.md (6)
35-36: Consistency: use “Released on …” (matches all other entries)Earlier sections use “Released on …”. Adjust for consistency.
Apply this diff:
-Released on Aug 18, 2025 +Released on Aug 18, 2025
39-42: Polish migration paragraph for clarity and grammarTighten wording, fix pluralization, and reduce ambiguity about recovery behavior.
Apply this diff:
-Update 6.8.0 came with a nasty small issue in one of the database migration. In the event your database is using a large amount of tags, the migration would fail due to duplicates conditions. We updated the migration file to handle this case and such that if you ended up in an incomplete database migration state, you could still get back up and running. +Update 6.8.0 shipped with a small issue in one of the database migrations. On instances with a large number of tags, the migration could fail due to duplicate-condition errors. We updated the migration to handle this case and ensured that if your update left the database in an incomplete migration state it can recover cleanly. -With this short notice, we also added a few small features that were nearly ready for version 6.8.0 but didn't make the cut. +With this patch release, we also added a few small features that were nearly ready for version 6.8.0 but didn't make the cut.
45-46: Grammar: “photos shown … any of the tags”Minor language fixes.
Apply this diff:
-* `new` #3624 : Add support for and/or in tag albums by @ildyria - > This change allows you to specify if you want the photos showed in a Tag album to match all the tags, or any of the tag. +* `new` #3624 : Add support for and/or in tag albums by @ildyria + > This change allows you to specify whether photos shown in a Tag album should match all tags or any of the tags.
47-49: Grammar: pluralize “feature”; clearer phrasing for selection behaviorApply this diff:
-* `new` #3504 : feat: Drag & select is back! by @ildyria - > One of the missing feature since version 4 was the ability to drag and select photos in the album view. This is now back. - > We tried to also make it more obvious what can and cannot be selected in such way on the album view. +* `new` #3504 : feat: Drag & select is back! by @ildyria + > One of the missing features since version 4 was the ability to drag-select photos in the album view. This is now back. + > We also made it clearer which items can and cannot be selected in this way on the album view.
50-52: Clarity: describe what changed in the migration fix more preciselyApply this diff:
* `fixes` #3626 : Fix migration when large amounts of tags are used by @ildyria - > The migration that was introduced in version 6.8.0 was failing when a large amount of tags were used. We fixed this by - > formatting the tags, and chunking at insert time to avoid large insert queries. + > The migration introduced in version 6.8.0 was failing when a large number of tags were used. This was fixed by + > normalizing tag values and chunking inserts to avoid oversized INSERT statements.
190-190: Nit: capitalize “Fix” after the colon for consistencyMost bullets capitalize the action after the colon.
Apply this diff:
-* `fixes` #3499 : fix header always showing up by @ildyria. +* `fixes` #3499 : Fix header always showing up by @ildyria.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
docs/releases.md(6 hunks)src/components/widgets/Announcement.astro(1 hunks)
🔇 Additional comments (6)
src/components/widgets/Announcement.astro (2)
17-18: LGTM: version link and label correctly bumped to v6.8.1Href and visible copy both point to v6.8.1. No structural changes introduced.
17-18: Confirm release tag timing to avoid a transient 404If this banner deploys before the GitHub tag is published, the link will 404 temporarily. Confirm the tag is live before merging, or hold merge until the Lychee release is published.
docs/releases.md (4)
105-105: LGTM: standardized to “fixes”The sweep to normalize “fix” → “fixes” in these entries improves consistency with the rest of the changelog.
Also applies to: 107-107, 109-109, 111-111, 112-112, 113-113, 115-115, 117-117
165-165: LGTM: wording reads wellEntry title is clear and consistent with neighboring items.
226-226: LGTMNo issues spotted.
492-492: LGTMReads consistently with the rest of the document.
1 participant
Summary by CodeRabbit
Documentation
Chores