Skip to content

Comments

docs: v3.27.0 release notes#334

Merged
hannesrudolph merged 1 commit intomainfrom
docs/release-notes-v3.27.0
Sep 6, 2025
Merged

docs: v3.27.0 release notes#334
hannesrudolph merged 1 commit intomainfrom
docs/release-notes-v3.27.0

Conversation

@hannesrudolph
Copy link
Collaborator

@hannesrudolph hannesrudolph commented Sep 6, 2025

This PR adds the v3.27.0 release notes and updates navigation:\n\n- Added release notes: docs/update-notes/v3.27.0.mdx\n - Highlights Edit/Delete Message with auto-checkpointing (merged analysis of PRs #7447 and #7713)\n - Reworded bug fixes to 'Fixes an issue where ...' as requested\n - Expanded frontmatter keywords for discoverability\n- Updated index: docs/update-notes/index.md (added 3.27.0 at top, 2025-09-05)\n- Updated sidebar: sidebars.ts (added 3.27 section with 3.27.0)\n\nTemporary analysis files under .roo/tmp/release-notes were cleaned up and are not included.\n\nScreens/links:\n- Release file: /update-notes/v3.27.0\n- Index: /update-notes\n


Important

Adds v3.27.0 release notes, updates documentation index and sidebar, and cleans up temporary files.

  • Release Notes:
    • Adds v3.27.0.mdx with details on message editing/deletion with rollback checkpoints, Chutes provider update, and various bug fixes.
    • Rewords bug fixes to start with 'Fixes an issue where...'.
    • Expands frontmatter keywords for better discoverability.
  • Documentation Index:
    • Updates index.md to include version 3.27.0 at the top.
  • Sidebar:
    • Updates sidebars.ts to add a new section for version 3.27 with 3.27.0.
  • Misc:
    • Cleans up temporary analysis files under .roo/tmp/release-notes.
    • Renames Release Notes Writer to 📝 Release Notes Writer and Documentation Writer to 📖 Documentation Writer in .roomodes.

This description was created by Ellipsis for 0c9afb5. You can customize this summary. It will automatically update as commits are pushed.

@vercel
Copy link

vercel bot commented Sep 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
roo-code-docs Ready Ready Preview Comment Sep 6, 2025 0:28am

Copilot AI review requested due to automatic review settings September 6, 2025 00:27
@hannesrudolph hannesrudolph merged commit de5a047 into main Sep 6, 2025
2 of 3 checks passed
@hannesrudolph hannesrudolph deleted the docs/release-notes-v3.27.0 branch September 6, 2025 00:28
@github-project-automation github-project-automation bot moved this from Triage to Done in Roo Code Roadmap Sep 6, 2025
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds v3.27.0 release notes documentation and updates navigation structure to include the new version. The release highlights message editing/deletion features with automatic checkpoints, provider updates, and various bug fixes.

  • Adds comprehensive v3.27.0 release notes with feature highlights and bug fixes
  • Updates navigation sidebar and index to include the new version
  • Creates documentation follow-up tracking for related feature documentation updates

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
sidebars.ts Adds new 3.27 section with 3.27.0 entry to navigation
docs/update-notes/v3.27.0.mdx Creates release notes with features, improvements, and fixes
docs/update-notes/index.md Adds 3.27.0 entry at top of version index
docs/features/checkpoints.mdx Updates checkpoint documentation to reflect new auto-checkpoint behavior
docs/basic-usage/the-chat-interface.md Updates interface description for plus button and mode selector
.roomodes Updates mode display names with emojis
.roo/tmp/release-notes/docs_followups_v3.27.0.md Temporary tracking file for documentation follow-ups

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment on lines 25 to 26
---

Copy link

Copilot AI Sep 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are duplicate horizontal rule separators (lines 24-25) which creates unnecessary visual clutter. Remove one of the --- lines.

Suggested change
---

Copilot uses AI. Check for mistakes.
#### Git LFS Patterns

Patterns defined in your workspace's `.gitattributes` for Git LFS are read and added to checkpoint exclusions. This helps avoid tracking large LFS-managed assets in the shadow repository.

Copy link

Copilot AI Sep 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new section about Git LFS patterns lacks detail about how users can configure these patterns or what happens when they're present. Consider adding an example of what LFS patterns look like in .gitattributes and how they affect checkpoint behavior.

Suggested change
To configure Git LFS patterns, add entries to your `.gitattributes` file in the root of your workspace. For example:
```gitattributes
# Track all PNG images with Git LFS
*.png filter=lfs diff=lfs merge=lfs -text
# Track all files in the 'large-data' directory
large-data/** filter=lfs diff=lfs merge=lfs -text

When these patterns are present, any files matching them will be excluded from checkpoint tracking. This means:

  • LFS-managed files will not be included in checkpoint commits or diffs.
  • Changes to these files will not trigger checkpoint creation.
  • This prevents large binary files from bloating the shadow repository and keeps checkpoint operations fast.

Note: You can edit .gitattributes at any time to update which files are managed by LFS and excluded from checkpoints.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant