Creating Release Notes for 1.0 #432
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added the draft release notes for 1.0, updated mkdocs and release notes md with paths
updated release date and number
small content update for upgrade considerations
Codecov ReportAll modified and coverable lines are covered by tests ✅
❌ Your project status has failed because the head coverage (84.65%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## release-17.5.2 #432 +/- ##
==================================================
- Coverage 84.66% 84.65% -0.01%
==================================================
Files 21 21
Lines 2589 2588 -1
Branches 402 401 -1
==================================================
- Hits 2192 2191 -1
Misses 316 316
Partials 81 81
🚀 New features to boost your workflow:
|
version variable was funky, messing with mkdocs serve, so I fixed it
changed the title of the pdf to: Percona Transparent Database Encryption for PostgreSQL
updated the ToC names to make them in line with style guide
small fix to versions, instead of RC2 I mentioned all previous versions
dutow
reviewed
Jun 18, 2025
|
|
||
| ## Upgrade considerations | ||
|
|
||
| `pg_tde` 1.0 is not backward compatible with previous `pg_tde` versions (like Release Candidate 2) due to significant changes in code. This means you cannot directly upgrade from one version to another. You must [uninstall](../how-to/uninstall.md) `pg_tde` first and then [install](../install.md) and configure the new 1.0 version. |
There was a problem hiding this comment.
Uninstall is not enough, use a clean installation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added initial files and modifications to include 1.0 release notes to the TOC and variables. Updates: