-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monorepo versioning #72
Labels
Comments
We can postpone the version checks implementation until the first infrastructure breaking check is introduced. |
Anyone with experience in publishing indirectly-depending packages from a monorepo is very welcome to share their thoughts on this 🤗 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
By the time this issue is created, there're two packages in this monorepo:
basti
)basti-cdk
)Suggested versioning strategy
basti
andbasti-cdk
are both versioned independently following semantic versioning.A new major version is released in two cases
basti-cdk
property or abasti
CLI option has been renamed.init
command orbasti-cdk
infrastructure is no longer compatible with the existing versions of the Basti CLIconnect
command.Newer versions of Basti CLI must support connecting to any older minor and major version of the infrastructure.
basti connect
command checks if the infrastructure was initialized with the satisfying major version of Basti CLI or Basti CDK. If not, the user is asked to update to the latest version of Basti CLI (which must support the newer infrastructure).The text was updated successfully, but these errors were encountered: