Skip to content

Upgrade policy for 1.2.0 - #2001

Draft
davidmckayv wants to merge 1 commit into
mainfrom
cloud/upgrade-policy-1.2.0
Draft

davidmckayv wants to merge 1 commit into
mainfrom
cloud/upgrade-policy-1.2.0

Conversation

@davidmckayv

Copy link
Copy Markdown
Contributor

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 version to v1.2.0-rc.1 and 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: adds 0151_sign_up_switch, where 1.1.3 left the database.
  • launcherApi stays 1, so the 1.1 apps still start a 1.2.0 server.
  • requiresDowntime stays false.

Before this merges: database.to still says 0151_sign_up_switch. It moves to the last migration the 1.2.0-rc.1 server applies once tonight's server changes are in, and requiresDowntime is checked against those migrations and the chart's annotation. Publishing refuses the policy until to matches, and says what to set.

Checked: tests/release-policy.test.ts, scripts/release-prepare.test.ts and scripts/release-version.test.ts pass (58). The publish-time database check, run against the real tags and the release manifests each starting release attached, accepts this from list. A dry run of Create release PR (minor, rc) from main gives v1.2.0-rc.1 on a new release/1.2.

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant