mongo migrate: update to mongo 7.0 + set feature compatibility. #3078
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
- set feature compatibility version to be 7.0 to support future upgrades - allow updating feature compatibility version on startup - fixes #2680
tw4l
approved these changes
Dec 11, 2025
Member
tw4l
left a comment
tw4l
left a comment
There was a problem hiding this comment.
Tested locally following the instructions in this PR. Verified that the compatibility version upgrade to 7 was logged in the migrations container, the database image was upgraded, and I'm still able to run crawls, see existing data, and otherwise do everything I expect to be able to do in Browsertrix following the upgrade.
tw4l
reviewed
Dec 11, 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.
When switching from 6.0 -> 7.0, mongo remains in '6.0' compatibility mode, so we need to set it to use 7.0 features.
This allows for eventual default image upgrade to mongo 8.0. To do that, we first need to update to 7.0 and update flag to have it not stay in 6.0-compatibility mode. 8.0 does not have 6.0-compatibility mode, so direct update is not possible, unfortunately.
Browsertrix already works with 8.0, but the default image needs to be upgraded to 7.0 first before upgrading to 8.0 for this reason -- it's not possible to update from mongo 6 to mongo 8 directly.
This should be done first thing so better to do it before db migrations.
Testing
migrationsinit container.