Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Publish on crates.io #77

Closed
colindean opened this issue Sep 19, 2023 · 4 comments
Closed

Publish on crates.io #77

colindean opened this issue Sep 19, 2023 · 4 comments

Comments

@colindean
Copy link
Contributor

Splitting off from #66 (comment) and #66 (comment), it'd be great if this was uploading to crates.io on release.

https://doc.rust-lang.org/cargo/reference/publishing.html

https://users.rust-lang.org/t/does-anyone-use-github-actions-to-run-cargo-publish/92374
@lafrenierejm lafrenierejm mentioned this issue Dec 24, 2023
Merged
@lafrenierejm lafrenierejm mentioned this issue Feb 19, 2024
Merged
sirwart pushed a commit that referenced this issue Feb 24, 2024
@lafrenierejm
Add publish-crate step to release workflow (#85)
ef54b36 
Addresses #77.

This new step requires the presence of a GitHub Actions Secret named CRATES_IO_API_TOKEN with access to publish the ripsecrets crate.

Dependencies were updated to avoid versions that have been yanked.
@lafrenierejm
Copy link
Contributor

Following #85, the release Actions workflow now publishes the crate to crates.io. The crate should become available the next time a new version is tagged.

@lafrenierejm
Copy link
Contributor

@sirwart Following up on this and #66 (comment) again. Have you given any more thought to triggering the release workflow?

@lafrenierejm
Copy link
Contributor

@sirwart Gentle nudge to publish a crate. :)

@sirwart
Copy link
Owner

sirwart commented Apr 20, 2024

@lafrenierejm just published!

@sirwart sirwart closed this as completed Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@colindean @sirwart @lafrenierejm