Repository navigation
Upgrade policy for 1.2.0 - #2001
Draft
davidmckayv wants to merge 1 commit into
Draft
davidmckayv wants to merge 1 commit into
davidmckayv wants to merge 1 commit into
Conversation
Names v1.2.0, upgrades from v1.1.3 (database 0151_sign_up_switch) beside every release before it. database.to moves to the last migration of the 1.2.0-rc.1 server before this merges.
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
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.
The upgrade policy for 1.2.0, written before the release PR so the first candidate, 1.2.0-rc.1, is cut from a commit whose policy already names the release. Its candidates and final share it: Create release PR moves
versiontov1.2.0-rc.1and back, and changes nothing else.version: v1.2.0.upgrade.fromVersions: adds v1.1.3. Every 1.1.x release stays listed, so OpenBot (Self-Contained) on any 1.1 release upgrades its server to 1.2.0 at the next Start, which is what puts the move to OpenBot Cloud in front of those people.database.from: adds0151_sign_up_switch, where 1.1.3 left the database.launcherApistays 1, so the 1.1 apps still start a 1.2.0 server.requiresDowntimestays false.Before this merges:
database.tostill says0151_sign_up_switch. It moves to the last migration the 1.2.0-rc.1 server applies once tonight's server changes are in, andrequiresDowntimeis checked against those migrations and the chart's annotation. Publishing refuses the policy untiltomatches, and says what to set.Checked:
tests/release-policy.test.ts,scripts/release-prepare.test.tsandscripts/release-version.test.tspass (58). The publish-time database check, run against the real tags and the release manifests each starting release attached, accepts thisfromlist. A dry run of Create release PR (minor, rc) from main gives v1.2.0-rc.1 on a new release/1.2.