-
Notifications
You must be signed in to change notification settings - Fork 140
Switch version numbers to 4.0, enable builds #7623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
Redocly previews |
There was a problem hiding this 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 upgrades the Sync Gateway release to 4.0.0, enables build numbering, and cleans up obsolete configurations and stages.
- Bumps
manifest/default.xml
release to 4.0.0 and setsstart_build
to 123. - Removes the standalone
manifest/4.0.xml
entry and updates that file’s revision tomain
. - Updates all OpenAPI specs’
version
to 4.0, drops a stale test comment, and removes the old Jenkinsanemone
stage.
Reviewed Changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.
Show a summary per file
File | Description |
---|---|
manifest/product-config.json | Updated default manifest release to 4.0.0, changed start_build , removed the 4.0 entry |
manifest/4.0.xml | Switched sync_gateway project revision from release/anemone to main |
docs/api/public.yaml (and others) | Updated version field from '3.3' to '4.0' in all public and Capella specs |
base/main_test_bucket_pool.go | Deleted an outdated “anemone release” comment |
Jenkinsfile | Removed the anemone stage from the pipeline |
Comments suppressed due to low confidence (2)
manifest/product-config.json:728
- Removing the
manifest/4.0.xml
entry may skip building that manifest unless it's included elsewhere. Verify that its removal won’t prevent the 4.0 pipeline from executing.
"trigger_blackduck": true,
docs/api/public.yaml:17
- [nitpick] The release version in manifest is
4.0.0
but the OpenAPI specs use4.0
. For consistency and clarity, consider using the full semantic version4.0.0
here.
version: '4.0'
bbrks
requested changes
Jul 10, 2025
bbrks
approved these changes
Jul 10, 2025
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.
Switch version numbers to 4.0, enable builds
I think 123 is the right build number to start on. 3.3.0 (former main) builds are going to be 286, but this continuity isn't a problem.