-
Notifications
You must be signed in to change notification settings - Fork 542
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
run cargo publish, package #1540
base: 0.5.x
Are you sure you want to change the base?
run cargo publish, package #1540
Conversation
9e75a32
to
fc3e640
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 0.5.x #1540 +/- ##
=======================================
Coverage 93.96% 93.96%
=======================================
Files 37 37
Lines 16662 16662
=======================================
Hits 15656 15656
Misses 1006 1006 ☔ View full report in Codecov by Sentry. |
35da889
to
3d60ea0
Compare
3d60ea0
to
aa6a2d5
Compare
Thank you! What errors would this catch that our regular build and test CI runs don't catch? |
Just added a similar CI job for chrono-tz in chronotope/chrono-tz#158. @jtmoon79 Want to finish up this PR? |
steps: | ||
- uses: actions/checkout@v4 | ||
- uses: dtolnay/rust-toolchain@stable | ||
- run: cargo publish --locked --dry-run ${{ env.ALL_NON_EXCLUSIVE_FEATURES }} |
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.
We don't need --locked
without a cargo.lock
.
Test that
cargo publish
andcargo package
succeed.