Update dependency bazel_gazelle to v0.28.0 #2
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.
This PR contains the following updates:
0.17.0
->v0.28.0
Release Notes
bazelbuild/bazel-gazelle
v0.28.0
Compare Source
What's Changed
visibility
attribute forgazelle
macro to resultingsh_binary
by @cgrindel in https://github.com/bazelbuild/bazel-gazelle/pull/1340go_proto_library
compilers by @fmeum in https://github.com/bazelbuild/bazel-gazelle/pull/1348gazelle_generation_test
respect out suffix when generating golden files by @blorente in https://github.com/bazelbuild/bazel-gazelle/pull/1352gazelle_generation_test
by @charlesoconor in https://github.com/bazelbuild/bazel-gazelle/pull/1351New Contributors
Full Changelog: bazel-contrib/bazel-gazelle@v0.27.0...v0.28.0
v0.27.0
Compare Source
What's Changed
go list -m -json
errors correctly by @fmeum in https://github.com/bazelbuild/bazel-gazelle/pull/1301New Contributors
Full Changelog: bazel-contrib/bazel-gazelle@v0.26.0...v0.27.0
v0.26.0
Compare Source
What's Changed
patch
from@bazel_tools//tools/build_defs/repo:utils.bzl
by @bozaro in https://github.com/bazelbuild/bazel-gazelle/pull/1269New Contributors
Full Changelog: bazel-contrib/bazel-gazelle@v0.25.0...v0.26.0
WORKSPACE
codeDefine your own dependencies here using go_repository.
Else, dependencies declared by rules_go/gazelle will be used.
The first declaration of an external repository "wins".
v0.25.0
: v0.25.0Compare Source
Go changes
go_repository
rules now default to this mode, showing significant performance improvements for some repo rules by @blico in https://github.com/bazelbuild/bazel-gazelle/pull/1201go_repository
rules no longer log Gazelle warnings, unlessdebug
mode is explictly set by @blico in https://github.com/bazelbuild/bazel-gazelle/pull/1205canonical_id
attribute forgo_repository
by @kmicklas in https://github.com/bazelbuild/bazel-gazelle/pull/1121Proto changes
proto_library
generation by @wolfd in https://github.com/bazelbuild/bazel-gazelle/pull/1033General changes
rule.AddAlias
func to support loading aliased symbols by @dorfire in https://github.com/bazelbuild/bazel-gazelle/pull/1127FixLoad
now generatesload
statements for helper functions by @illicitonion in https://github.com/bazelbuild/bazel-gazelle/pull/1164Full Changelog: bazel-contrib/bazel-gazelle@v0.24.0...v0.25.0
WORKSPACE
codeDefine your own dependencies here using go_repository.
Else, dependencies declared by rules_go/gazelle will be used.
The first declaration of an external repository "wins".
v0.24.0
: v0.24.0Compare Source
This release requires rules_go 0.29 to support the retirement of
go_tool_library
.IMPORTANT
This release includes many new dependencies. Please be sure that your own workspace's dependencies are declared PRIOR to
gazelle_dependencies()
, or else they may be overridden. See the prompt block comment in the boilerplate below.Changes
go_repository
rules (#1090)Fixes
Full Changelog: bazel-contrib/bazel-gazelle@v0.23.0...v0.24.0
WORKSPACE
codeDefine your own dependencies here using go_repository.
Else, dependencies declared by rules_go/gazelle will be used.
The first declaration of an external repository "wins".
v0.23.0
: v0.23.0Compare Source
Changes
CXXFLAGS
andCPPFLAGS
#cgo
directives are separated intocxxopts
andcppopts
attributes, respectively. Thanks @otan.gazelle
rule now supports theupdate-repos
command.gazelle
rule now has adata
attribute and expands$(location)
within arguments.go_repository
'sbuild_naming_convention
is now considered when resolving external dependencies. If a repository already has build files, this attribute may be set to indicate which naming convention it follows.embedsrcs
attributes are generated for packages that contain//go:embed
directives.proto_strip_import_prefix
may be set in the root build file. Thanks @linzhp.WORKSPACE
codev0.22.3
: v0.22.3Compare Source
Bug fixes
-mode=diff
treats empty build files correctly. (thanks @vpanta)WORKSPACE code
v0.22.2
Compare Source
Compatibility
go_rule
function from rules_go, which will be removed in 0.25. This should improve compatibility with future versions.WORKSPACE code
v0.22.1
Compare Source
Bug fixes
Go
WORKSPACE
if the repositoryio_bazel_rules_go
hasn't been fetched yet.gazelle_binary
rule should now work correctly with previous versions of rules_go.import
andimport_alias
naming conventions, dots will be replaced with underscores in generated test names. This avoids generating targets that have the same names as source files.update-repos -from_file=go.mod
should no longer fail mysteriously whengo.mod
has areplace
directive that uses a relative path. Local replacements are still not supported though. (thanks @dragonsinth)WORKSPACE code
v0.22.0
Compare Source
Changes
foo
if its import path ends withfoo
instead ofgo_default_library
. Similarly, a test will be namedfoo_test
instead ofgo_default_test
.# gazelle:go_naming_convention
directive or the-go_naming_convention
flag. Valid values areimport
,go_default_library
, andimport_alias
. Gazelle will rename existing targets the next time it runs after a change.go_repository
uses theimport_alias
naming convention by default, so either the old or new names may be used.# gazelle:go_generate_proto
directive, which instructs the Go extension whether to generatego_proto_library
rules forproto_library
generated by the proto extension (thanks @linzhp).resolve.CrossResolver
interface. This is now used for resolve proto imports in Go (thanks @blico).update-repos
command, the-build_directives
flag may be used to set thebuild_directives
attribute on generated repositories (thanks @Helcaraxan).update-repos
command, new rules and macros will be inserted higher inWORKSPACE
, abovego_rules_dependencies
andgazelle_dependencies
if possible, to make it easier to override indirect dependencies.Compatibility
gazelle_binary
no longer supports mode attributes such asgoos
,race
, andgotags
. These depended on internal implementation details in rules_go. If you need to build agazelle_binary
for a platform other than the host, use command-line flags such as--platforms
and--@​io_bazel_rules_go//go/config:race
or use a transition.WORKSPACE code
v0.21.1
Compare Source
Bug fixes
internal
directories. Previously,internal visibility was applied to packages in subdirectories of
internal
,directories, not
internal
directories themselves. Thanks to @robfig.go_repository
no longer runscat
, andgenrules
are replaced with nativerules to reduce dependence on msys2 on Windows. Thanks to @tomlu.
select
expressions are no longer emitted for platforms that aren'tsupported by the current version of rules_go.
v0.21.0
Compare Source
# gazelle:exclude
directives now accept patterns with*
and**
wildcards. (thanks @kalbasit)-lang
flag may now be used to select which language extensions should be run. By default, all extensions Gazelle was built with will run. (thanks @robfig)proto_library
rules with one or more sources in common with the generated rule, even if the rule has been renamed. (thanks @linzhp)v0.20.0
Compare Source
General changes
update-repos
is invoked with-to_macro
, Gazelle will add a call to the macro and a# gazelle:repository_macro
directive to WORKSPACE if neither is present.Go changes
go_repository
rules when two module paths differ only in case. Thanks to @linzhp.Proto changes
load
statements forproto_library
to comply with--incompatible_load_proto_rules_from_bzl
. Thanks to @Yannic.v0.19.1
Compare Source
Changes
go_repository
stderr output.SSL_CERT_FILE
andSSL_CERT_DIR
are passed through to tools used bygo_repository
.v0.19.0
Compare Source
General changes
# gazelle:repository
directive is now supported in WORKSPACE files. Gazelle will behave as if a repository rule were declared with the given kind and attributes. This may override other declared rules. This is useful for declaring rules that appear in other files and can't be managed with#gazelle:repository_macro
. Thanks to @blico.update-repos
command now accepts versions for each argument, for example,update-repos github.com/sirupsen/logrus@v1.4.0
. For Go, the version suffixes follow the same format thatgo get
accepts in module mode. Thanks to @weixiao-huang.Go changes
go_repository
has better support for visibility across submodules. For example,cloud.google.com/logging
may now depend on internal packages incloud.google.com
, when both modules are unmodifiedgo_repository
rules. Previously, this requiredvisibility
attributes to be patched into the parent module.go_repository
now handles WORKSPACE-based configuration more efficiently. A configuration file is derived from the relevant parts of WORKSPACE and any functions declared with# gazelle:repository_macro
.go_repository
rules are re-evaluated when the configuration file changes, not when WORKSPACE changes. Previously, non-Go-related changes to WORKSPACE would causego_repository
to be re-evaluated. Thanks to @blico.go_repository
now accepts abuild_directives
attribute, a list of directives to write into the root build file before running Gazelle. Thanks to @linzhp.# gazelle:go_visibility
directive may be used to add labels to visibility attributes of Go rules. Thanks to @linzhp.go_library
srcs
if they are consumed by another rule through thesrc
orsrcs
attributes. Thanks to @linzhp.Proto changes
v0.18.2
Compare Source
Changes
gazelle_binary
rules in Go 1.13.v0.18.1
Compare Source
This release is a quick fix to address an issue with
go_repository
on Windows.v0.18.0
Compare Source
Compatibility
rules_go
0.19.0 or later is now required. Older versions are not supported but may still work, depending on what features are needed.General changes
gazelle update-repos
now supports the flag-to_macro=file.bzl%macro
. Instead of writing new repository rules to WORKSPACE, rules will be written to a function in a separate .bzl file. This helps keep related rules together. Thanks to @blico!# gazelle:repository_macro file.bzl%macro
may be used in WORKSPACE to declare a macro generated with the above flag.gazelle update-repos
will automatically update rules declared in the named macros instead of adding them to WORKSPACE. The directive may be repeated for multiple macros.gazelle fix
andgazelle update
will also read workspaces declared in these macros to find known repository roots and names. Thanks again to @blico!# gazelle:exclude .
may now be written to skip updating the current directory and subdirectories. Previously,exclude
only applied to files and subdirectories.Go changes
go_repository
can now download modules. To download a module, set theversion
andsum
attributes instead ofurls
(for HTTP) orcommit
ortag
(for VCS downloads).go_repository
will download and verify the specified module withgo mod download
. The environment variablesGOPROXY
,GOPRIVATE
,GONOPROXY
,GOSUMDB
, andGONOSUMDB
are observed, so be sure to set these for private modules when using go1.13 or later.gazelle update-repos <path>
will add or updatego_repository
rules in module mode.gazelle update-repos -from_file=go.mod
will also add or update rules in module mode.go_repository
. There are now separate tools and cache workspaces. Modules are downloaded into the cache. When Gazelle is updated, it should not be necessary to re-download modules unless the implementation of the cache changes. The environment variableGO_REPOSITORY_USE_HOST_CACHE
may be set to1
to use$GOPATH/pkg/mod
as a module cache instead of the cache workspace.go_repository
now provides areplace
attribute in module mode, analogous toreplace
in a go.mod file. Theversion
andsum
attributes are used on the replacement, but build files will be generated with theimportpath
of the original module.gazelle update-repos -from-file=go.mod
will addreplace
attributes automatically (thanks to @bigkraig!).gazelle update-repos
now supports the flag-prune
, which may be used with-from_file
. When enabled, Gazelle will removego_repository
rules that no longer have equivalent repos in go.mod or Gopkg.lock. Thanks to @blico!go_repository
, Gazelle now supports minimal module compatibility. For v2+ modules, Gazelle will generateimportpath_aliases
attributes sogo_libraries
may be imported without the semantic import version suffix by non-modularized packages.Proto changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.