release.yml skips cargo-semver-checks when crates.io answers with any error
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read the “Look for a published baseline” step around lines 78–86 of release.yml and inspect the relevant checks in ci-scripts. Make the step distinguish a 404 from other non-200 responses, with non-404 errors failing or retrying. Done when a stand-in returning 503 fails the step.
Written by the indexing model from the issue text.
Description
Today — the "Look for a published baseline" step (release.yml ~78-86) sets found=true only for HTTP 200, so a 429, 500 or 503 from crates.io is read as "first release, no baseline" and the semver gate is skipped before publishing.
Fix — distinguish 404 (no crate) from any other non-200 (fail the job, or retry with backoff); since every crate now exists, a missing baseline should fail rather than skip.
Done when — a stand-in returning 503 fails the step; tested in ci-scripts.
Found in the 0.3.0 review; published 0.2.0 has the same code.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 2
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vyncint/oxidelake
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
All issues in vyncint/oxidelake
Similar issues
-
bug duplicate priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
storytold/vectorcraft#6956 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug multiple issues priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/gridcraft#3928 · 1 comment ·
Maintainers usually reply within 1 day
-
crate-drift
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
po4yka/rust-skills#33 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
svix/svix-webhooks#2808 ·
Maintainers usually reply within 1 day