fix: Update variables for publish crate action#32
Merged
Conversation
Part of our CI being broken, is that clippy lints like this were not being caught.
The variables had been changed, which was causing the CI job to fail. And the CI job isn't marked as required, so nobody noticed.
fb7fc46 to
ec0ec43
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #32 +/- ##
==========================================
- Coverage 74.36% 74.18% -0.19%
==========================================
Files 5 5
Lines 277 275 -2
==========================================
- Hits 206 204 -2
Misses 71 71
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Harness.
|
emgrav
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The variables had been changed, which was causing the CI job to fail. And the CI job isn't marked as required, so nobody noticed.