fix: Fix handling of --skip-first argument Update release_crates.sh #7087
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.
I noticed that the script didn't handle the case where the
-s
or--skip-first
argument was provided without a value. This could lead to unexpected behavior. I've added a check to ensure a value is provided when using--skip-first
. If no value is given, the script will now print an error message and exit gracefully. This makes the script more robust and prevents potential issues.Changes:
--skip-first
argument to ensure a numeric value is provided.Thanks for Starknet!