Skip to content

fix(ci): handle new crate addition in semver-check #1769

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

Merged
gh-worker-dd-mergequeue-cf854d merged 1 commit into from
Mar 20, 2026
Merged

fix(ci): handle new crate addition in semver-check #1769

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions scripts/semver-level.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,11 @@ compute_semver_results() {
DETAILS=$(echo "$SEMVER_OUTPUT" | grep -A 1000 "^--- failure" | head -100 || echo "$SEMVER_OUTPUT" | tail -50)
log_verbose "Detected semver violations (major change)" >&2
log_verbose "$SEMVER_OUTPUT" >&2
elif echo "$SEMVER_OUTPUT" | grep -qF "package \`$crate\` not found"; then
# The crate doesn't exist in the baseline — it's a new crate being added
LEVEL="minor"
REASON="New crate (not present in baseline)"
log_verbose "New crate '$crate' not found in baseline, treating as minor change" >&2
else
echo "Error running cargo-semver-checks: $SEMVER_OUTPUT" >&2
exit $SEMVER_EXIT_CODE
Expand Down
Loading