Prepare release v0.33.0

[fmeum]

Release Notes

Breaking changes

• cover has been removed in v0.32.0. Please leave a comment if you are affected by this.

Deprecations

• The asm, compile, and pack action generators provided by go_context are deprecated and planned for removal in version v0.36.0. Please leave a comment on the tracking bug if archive and link are not suitable replacements for your use cases.

Bug Fixes

• @sluongng fixed a race condition that could cause non-sandboxed builds of go_test targets to fail (compilepkg: fix race when run without sandbox #3145)
• @abhinav made //go:embed work with go_path (go_path: Support go:embed #3163)
• @xytan0056 made gopackagesdriver work with Go 1.18 (Fix gopackagesdriver for Go 1.18 by replicating stdlib and add test for stdliblist.go #3157)
• @nickgooding ensured that gomock can be used with any Gazelle naming convention (Add go_default_library alias for gomock targets #3155)
• go_library targets using CGo can now reference unresolved symbols (Fix linker error if go_library with cgo references unresolved symbol #3174)

Thanks to all of the contributors!

Compatibility

The minimum required version of Bazel remains at 4.2.1.

Updated dependencies

• Updated org_golang_x_sys, org_golang_x_xerrors, org_golang_google_genproto, go_googleapis to their most recent commit as of 2022-06-05

As always, you can use higher versions of rules_go's dependencies by declaring them in WORKSPACE before calling go_rules_dependencies. Lower versions may work but are not supported.

WORKSPACE code

// TBD after release

[sluongng]

Would be nice to get a gazelle release coupled with this. ❤️

[sluongng]

Please leave a comment on the tracking bug if archive and link are not suitable replacements for you use cases.

s/you/your/

[fmeum]

Will try to fix #3178 for this release.

[linzhp]

Do you want to upgrade x_tools too? It's been while since last upgrade

[fmeum]

I remember you saying something about gazelle having to update x_mod first. Has that been done?

[linzhp]

yeah, but I am wondering whether we can make rules_go not relying on Gazelle's version of x_mod. If that's not possible, maybe we should upgrade x_mod in Gazelle and release a new version of Gazelle? It's been a while since last release.

[fmeum]

That seems difficult - we would probably have to get it with a git_repository and patch in BUILD files. Should I also do the Gazelle release? I don't know the project well though.

[fmeum]

Confirmed that Gazelle tests pass with rules_go at this PR with the latest commit fixing bzl_library deps.

[sluongng]

just a small note: we should look into how to de-noise the *.patch files. All the diff seems to be just changing the time stamp in the generated diff which is not useful to review.

[sluongng]

https://github.com/bazelbuild/rules_go/blob/master/go/tools/releaser/upgradedep.go#L539-L559 It seems like we do intended to sanitize the patch file from timestamp, but there is a bug that make it fail? 🤔