-
Notifications
You must be signed in to change notification settings - Fork 32
fix: v9 module path release workflow #559
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| // @oagen-ignore-file | ||
|
|
||
| module github.com/workos/workos-go/v8 | ||
| module github.com/workos/workos-go/v9 | ||
|
|
||
| go 1.23 | ||
|
|
||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
grepreturns emptyThe
CURRENT_MAJORextraction on line 50 usesgrep -oPwith no fallback. If the regex matches nothing (e.g., the module path ever lacks a/vNsuffix, orgo.modis temporarily in a state the pattern doesn't cover),CURRENT_MAJORis silently set to an empty string. The comparison[ "" = "$NEW_MAJOR" ]then evaluates to false, so thesedcommands run withv${CURRENT_MAJOR}expanding to justv— they match nothing, no files change,git diff --staged --quietpasses, and the step exits 0 reporting "No changes to commit" without the migration having run.Adding
set -euo pipefailat the top of the script would cause the step to fail loudly instead, and an explicit guard (if [ -z "$CURRENT_MAJOR" ]; then echo "::error::..."; exit 1; fi) would make the failure mode even clearer. This code is identical to what was present before the reorder, so it's a pre-existing gap — but now that this is the first step to commit, a silent skip here is harder to detect in the PR.