Conversation
modified: docs/_templates/pdf_cover_page.tpl modified: docs/release-notes.md new file: docs/release-notes/2.11.0.md modified: mkdocs-base.yml modified: variables.yml
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation to release version 2.11.0 of Percona Backup for MongoDB, replacing the previous 2.10.0 version references throughout the documentation system.
- Updates version numbers from 2.10.0 to 2.11.0 across configuration files
- Adds comprehensive release notes for version 2.11.0 with new features and bug fixes
- Updates navigation structure to include the new release notes
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| variables.yml | Updates release version to 2.11.0 and adds release date |
| mkdocs-base.yml | Updates navigation to include 2.11.0 release notes |
| docs/release-notes/2.11.0.md | Adds complete release notes for version 2.11.0 |
| docs/release-notes.md | Adds 2.11.0 entry to the release notes index |
| docs/_templates/pdf_cover_page.tpl | Updates PDF cover page to reflect 2.11.0 version |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| - "{{pbm.full_name}} 2.11.0 ({{date.2_11_0}})": release-notes/2.11.0.md | ||
| - release-notes/2.10.0.md | ||
| - release-notes/2.9.1.md | ||
| - release-notes/2.9.0.md |
There was a problem hiding this comment.
The navigation structure is inconsistent. The 2.11.0 entry uses the full template format with name and date, while older entries (2.10.0, 2.9.1, 2.9.0) only reference the file path. All entries should follow the same format for consistency.
Updated compatibility matrix
Updated GCS page with a warning
it-percona
temporarily deployed
to
PBM-1616-Release-notes-2.11.0 - pbm-docs PR #301
Render
Destroyed
|
|
||
| ## Ensure successful upload of any size backup | ||
|
|
||
| When backup files are so large that they exceed the object size limit for backup storage, PBM now splits such files into pieces that fall within the size limit and uploads them to the storage. PBM names these pieces to identify and manage them later. The reverse process occurs during the data read for a restore: PBM merges the pieces into a single file and proceeds with the command execution. You can redefine the default size limit using PBM configuration and ensure your backups are uploaded regardless of the size. Learn more about how to do it in the [documentation](../features/split-merge-backup.md). |
There was a problem hiding this comment.
@boris-ilijic for incremental backups I guess these need to be redone right? In that case - it's worth to mention it.
5 participants
modified: docs/_templates/pdf_cover_page.tpl
modified: docs/release-notes.md
new file: docs/release-notes/2.11.0.md
modified: mkdocs-base.yml
modified: variables.yml