Skip to content

Don't set module version outside BCR#4381

Merged
fmeum merged 1 commit intomasterfrom
fmeum-patch-2
Jun 20, 2025
Merged

Don't set module version outside BCR#4381
fmeum merged 1 commit intomasterfrom
fmeum-patch-2

Conversation

@fmeum
Copy link
Copy Markdown
Member

@fmeum fmeum commented Jun 20, 2025

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

This results in an empty version when rules_go is used as an override, which should avoid the warning reported in #4380.

Which issues(s) does this PR fix?

Fixes #4380

Other notes for review

This results in an empty version when rules_go is used as an override, which should avoid the warning reported in #4380.

Fixes #4380
@fmeum fmeum merged commit 5e3cb43 into master Jun 20, 2025
4 checks passed
@fmeum fmeum deleted the fmeum-patch-2 branch June 20, 2025 15:35
@alexeagle
Copy link
Copy Markdown
Contributor

Oh we have to make this change in a lot of places!

@fmeum
Copy link
Copy Markdown
Member Author

fmeum commented Jun 23, 2025

It only really matters for modules whose version is read by a semver-aware module extension. It makes sense to change our recommendations, but we don't have to actively update all the modules out there.

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.

Mismatch between versions requested for Go module github.com/bazelbuild/rules_go:

3 participants