-
Notifications
You must be signed in to change notification settings - Fork 108
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
Adds improvements & new crates to publish-crates.sh
#2173
Conversation
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.
Thank you for doing this! This looks better than what I got from copilot in my spike of making these changes.
That said, I think it needs another quick pass.
Ideally these would also be separate changes since they're logically independent:
- Bump crate versions
- Add new crates to publish script
- Add new functionality to publish script
That said, they're all small and self-contained so I think it's okay to leave these in the same PR this time (as long as you're fine with all of them waiting to merge until all of them are approved).
Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
…x-publish' of github.com:clockworklabs/SpacetimeDB into tyler/bump-version-fix-publish
Created #2176 to track us investigating the |
publish-crates.sh
I moved the version bumps into #2177. |
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.
This version LGTM
Thank you for making the changes, this LGTM. |
Description of Changes
This PR modifies
publish-crates.sh
:--allow-dirty
which is forwarded tocrates publish
tyler@clockworklabs.io
andzeke@clockworklabs.io
to be an owner on all newly published cratesNOTE! I recommend we investigate https://github.com/crate-ci/cargo-release in the future rather than to improve this script ad infinitum.
API and ABI breaking changes
None
Expected complexity level and risk
1, it can only break this script, but nothing else.
Testing
I have not tested the new improvements to the script since it's quite hard to test without bumping the versions on things. The risk however is very low and I figure we can fix issues as they come.