Skip to content

fix(ci): replace \d with [0-9] in semver validation grep#561

Merged
olivermeyer merged 1 commit into
mainfrom
chore/fix-prepare-release
Apr 23, 2026
Merged

fix(ci): replace \d with [0-9] in semver validation grep#561
olivermeyer merged 1 commit into
mainfrom
chore/fix-prepare-release

Conversation

@olivermeyer

Copy link
Copy Markdown
Collaborator

Why?
The prepare-release workflow was rejecting valid semver inputs like 1.3.0 because the grep pattern used \d to match digits. \d is a PCRE extension and is not recognised by POSIX ERE (grep -E), the mode used on the GitHub Actions Ubuntu runner.

How?
Replace \d with [0-9] in the semver validation regex, making it valid POSIX ERE and portable across all GNU/Linux environments.

\d is a PCRE extension and not valid in POSIX ERE (grep -E). On the
GitHub Actions Ubuntu runner this caused valid versions like '1.3.0'
to always fail the semver validation check.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 23, 2026 12:15
@sonarqubecloud

Copy link
Copy Markdown

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes the prepare-release GitHub Actions workflow semver validation so it works correctly with POSIX ERE on Ubuntu runners (avoids using PCRE-only \d).

Changes:

  • Update the semver validation grep -E pattern to use [0-9] instead of \d.

@olivermeyer olivermeyer enabled auto-merge (rebase) April 23, 2026 12:28
@olivermeyer olivermeyer disabled auto-merge April 23, 2026 12:28
@olivermeyer olivermeyer enabled auto-merge (rebase) April 23, 2026 12:39
@olivermeyer olivermeyer merged commit 62aa11f into main Apr 23, 2026
28 checks passed
@olivermeyer olivermeyer deleted the chore/fix-prepare-release branch April 23, 2026 12:44
@codecov

codecov Bot commented Apr 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants