Conversation
Split the single shared version (APP_VERSION) into two independent counters: CLIENT_VERSION (root package.json, tagged v*) and SERVER_VERSION (packages/server/package.json, tagged server/v*). Migration tracking now uses SERVER_VERSION, so the DB version advances only on server releases — matching the reality that server releases are what ship schema changes. Rename scripts/release.ts -> scripts/release-client.ts (narrowed to the npm-published packages) and add scripts/release-server.ts (bumps the server-side packages in lockstep, tags server/v<x.y.z>). This lets us ship backwards-compatible server changes before the client catches up, without forcing a prod deploy on every npm release.
Match the SERVER_VERSION constant introduced in the previous commit. Also updates the downgrade-rejection error messages in both migration runners to say 'Server version' / 'upgrade the server' instead of the ambiguous 'App version' / 'upgrade the application'.
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
1 participant
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.
Split the single shared version (APP_VERSION) into two independent counters: CLIENT_VERSION (root package.json, tagged v*) and SERVER_VERSION (packages/server/package.json, tagged server/v*). Migration tracking now uses SERVER_VERSION, so the DB version advances only on server releases — matching the reality that server releases are what ship schema changes.
Rename scripts/release.ts -> scripts/release-client.ts (narrowed to the npm-published packages) and add scripts/release-server.ts (bumps the server-side packages in lockstep, tags server/v<x.y.z>). This lets us ship backwards-compatible server changes before the client catches up, without forcing a prod deploy on every npm release.