fix: pin platform package versions to exact release version#67
Merged
Conversation
Users were getting stale platform binaries after upgrade because the optional dependencies used >=0.1.1 which allowed package managers to resolve any cached older version. Pin to exact version and add a release workflow step to keep them in sync.
Deploying archgate-cli with
|
| Latest commit: |
ee58e3b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f2bb2115.archgate-cli.pages.dev |
| Branch Preview URL: | https://fix-pin-platform-package-ver.archgate-cli.pages.dev |
Override NpmProject.bump() to sync optionalDependencies after version bump, removing the need for a separate workflow step.
This was referenced Mar 17, 2026
Merged
Merged
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.
Summary
optionalDependenciesfor platform binary packages to the exact current version (0.11.0) instead of>=0.1.1Problem
Users running
archgate upgradewere getting stale platform binaries because>=0.1.1allowed package managers to resolve any cached/older version. For example, a user onarchgate@0.11.0could still havearchgate-win32-x64@0.10.0because it satisfies>=0.1.1.Test plan
bun run validatepasses