Sanitize 'since' input in prep-release workflow#9
Merged
bouzidanas merged 1 commit intomainfrom Dec 14, 2025
Merged
Conversation
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
1 participant
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.
Description:
This commit fixes a bug in the prep-release.yml GitHub Actions workflow that caused the
jupyter-releaser build-changelogcommand to fail.The
sinceinput for the workflow was being passed directly to the action, which could include newlines or other characters that would cause the underlyinggithub-activitytool to fail with aParserErrororHTTPError: 422.This change adds an intermediate step to sanitize the
sinceinput, ensuring that only the first line is used and passed to the release action. This prevents invalid characters from breaking the release preparation process.