We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v0.44.2
v0.35.0
7.0.0
Yes
Ubuntu x86_64
Local ubuntu, simple setup
Upgrade from v0.44.1 to v0.44.2
v0.44.1
No breaking change
ERROR: Error computing the main repository mapping: cannot load '@@bazel_features//:deps.bzl': no such file
After adding:
http_archive( name = "bazel_features", sha256 = "b8789c83c893d7ef3041d3f2795774936b27ff61701a705df52fd41d6ddbf692", strip_prefix = "bazel_features-1.2.0", url = "https://github.com/bazel-contrib/bazel_features/releases/download/v1.2.0/bazel_features-v1.2.0.tar.gz", ) load("@bazel_features//:deps.bzl", "bazel_features_deps") bazel_features_deps()
then go_rules_dependencies loads properly and build gives the same result as v0.44.1
go_rules_dependencies
This should probably be defined in the release message ?
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What version of rules_go are you using?
v0.44.2
What version of gazelle are you using?
v0.35.0
What version of Bazel are you using?
7.0.0
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
Ubuntu x86_64
Any other potentially useful information about your toolchain?
Local ubuntu, simple setup
What did you do?
Upgrade from
v0.44.1
tov0.44.2
What did you expect to see?
No breaking change
What did you see instead?
ERROR: Error computing the main repository mapping: cannot load '@@bazel_features//:deps.bzl': no such file
After adding:
then
go_rules_dependencies
loads properly and build gives the same result asv0.44.1
This should probably be defined in the release message ?
The text was updated successfully, but these errors were encountered: