-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Sign our releases #1347
Sign our releases #1347
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
6e98104
to
39dbdf7
Compare
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.
Challenge with changing release workflow is how to test it...
I suppose that we can trigger release-build.yml on any PR that modifies it and does a dry-run.
It would be great if we can add testing for our release pipeline, though it won't be easy to add so I won't make it a blocker for this PR |
yehmmmm I think we'll have to test this one live. I've run the scripts locally simulating the environment as best I can, though, so, not going in totally blind |
This uses an ephemeral key.
It writes the
[signing]
section to the Cargo.toml just before publish, so the Cargo.toml in the source remains without, which makes--git
installs work (just without verifying signatures).It uses rsign2 so we can install it via binstall (dogfooding!).