-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feat/check trader versions #236
base: main
Are you sure you want to change the base?
Conversation
exit 0 | ||
fi | ||
|
||
echo "Checking out matching trader versions. In case you want to skip this check add 'test' to the tag name. Ex. v0.1.0-rc50test" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this tag naming approved by @truemiller ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i believe this tag will break the cli's release process..
i think it's more strict than on javascript side. Yuri had tested v0.1.0-rcX.Y
last week, and it required a full bump for major.minor.patch instead..
however, we could adopt a more robust versioning approach here, and use dev
tags for tests moving forward, as we're currently just spamming rc
versions
see: https://peps.python.org/pep-0440/#public-version-identifiers
This PR adds support for checking if the trader versions match during a release.