Let users try v1.0-RC1 without changing the stable channel - #191
Open
guanzhousongmicrosoft wants to merge 9 commits into
Open
guanzhousongmicrosoft wants to merge 9 commits into
guanzhousongmicrosoft wants to merge 9 commits into
Conversation
guanzhousongmicrosoft
changed the title
guanzhousongmicrosoft
changed the title
xgerman
approved these changes
Sep 28, 2026
Signed-off-by: Guanzhou Song <guanzhousong@microsoft.com>
The pgNN-1.0.0 tags will move to the final 1.0 build; testers should pin pgNN-1.0.0-rc1. RC images exist for PostgreSQL 15-18, not only 17/18. Signed-off-by: Guanzhou Song <guanzhousong@microsoft.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
v1.0-RC1 is for trying 1.0, not a release we maintain. Like PostgreSQL betas or MongoDB RCs, it's opt-in: the package repository,
latestimage and default guides stay on v0.117-0, and the RC is labelled with no maintenance and no upgrade path.The site points RC testers at the docs page added in documentdb/docs#79 (
/docs/getting-started/release-candidate) instead of repeating it: a note at the top of the Linux packages guide, an RC row in the Docker tag table, and a note inPACKAGE-INSTALL.md. Merge together with docs#79, or the links 404.Also adds the extended-RUM warning to the extension-only section (
CASCADEdoesn't createdocumentdb_extended_rum, and index creation fails without it; true for v0.117-0 too), and a test that the guides' package download and source links match the mirrored release.