Skip to content
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

Release v0.36.3 #2946

Merged
merged 13 commits into from
Sep 4, 2024
Merged

Release v0.36.3 #2946

merged 13 commits into from
Sep 4, 2024

Conversation

sukunrt
Copy link
Member

@sukunrt sukunrt commented Aug 30, 2024

Same as master except

  • Make BlackHoleState type public 99433a2

joshklop and others added 13 commits August 19, 2024 10:32
* Add failing proto test

* Add a new proto compilation script

A proto file's *import path* is relative to one of the `--proto-path`s.

Previously, the proto files were compiled separately. Some invocations
used different values for the `--proto_path`, which led to inconsistent
import paths in proto file descriptors.

Typically, this wouldn't be a problem. However, if a downstream project
uses `protoregistry.GlobalFiles` to inspect proto dependencies, it will fail
to find a dependency's file descriptor when the dependency was compiled
with a different `--proto_path`.

By using a single script to generate all protobuf files, we can ensure
the `--proto_path` is always set to the same sane value (the root of the
project, as suggested in the [official documentation]).

[official documentation]: https://protobuf.dev/programming-guides/proto2/#importing

* Add go_package options so scripts/gen-proto.sh succeeds

* Remove undesirable `go:generate protoc` directives

* Run `go generate ./...`

* Script uses arrays, I think we need bash

---------

Co-authored-by: Marco Munizaga <git@marcopolo.io>
* Lint fixes

* Use latest go version for go-check

Fixes nil pointer issue in staticcheck

* Add test_analysis helper script

* Use custom go-test-template

* Add some tests to the test_analysis script

* Always upload test_results db

* Attempt to fix test on windows

* Better if statement

* Try to fix flaky test

* Disable caching setup-go on Windows

* Better if statement

* Tweak

* Always upload summary and artifact

* Close db

* No extra newline
Signed-off-by: bytetigers <bytetiger@icloud.com>
* chore: bump go.mod to Go 1.22 and run go fix

* Bump docker builder version

---------

Co-authored-by: Marco Munizaga <git@marcopolo.io>
* fix: allow punching undialable host public ip

fixes #2913

* chore: use interface listen addrs to enable dctur

* fix: filter public addresses

* chore: remove unused function

* chore: formatting

---------

Co-authored-by: Daniel N <2color@users.noreply.github.com>
@sukunrt sukunrt requested a review from MarcoPolo August 30, 2024 15:12
Copy link

Suggested version: 0.36.3

Comparing to: v0.36.2 (diff)

Changes in configuration file(s):

(empty)

gorelease says:

# diagnostics
go.mod: the following requirements are needed
	github.com/cheekybits/genny@v1.0.0
	github.com/fsnotify/fsnotify@v1.6.0
	github.com/go-task/slim-sprig@v0.0.0-20230315185526-52ccab3ef572
	github.com/golang/mock@v1.6.0
	github.com/hashicorp/golang-lru@v0.5.4
	github.com/libp2p/go-openssl@v0.1.0
	github.com/libp2p/go-yamux/v3@v3.1.2
	github.com/lucas-clemente/quic-go@v0.28.1
	github.com/marten-seemann/qtls-go1-16@v0.1.5
	github.com/marten-seemann/qtls-go1-17@v0.1.2
	github.com/marten-seemann/qtls-go1-18@v0.1.2
	github.com/marten-seemann/qtls-go1-19@v0.1.0
	github.com/mattn/go-pointer@v0.0.1
	github.com/onsi/ginkgo@v1.16.5
	github.com/spacemonkeygo/spacelog@v0.0.0-20180420211403-2296661a0572
	go.opencensus.io@v0.23.0
	gopkg.in/tomb.v1@v1.0.0-20141024135613-dd632973f1e7
Run 'go mod tidy' to add missing requirements.
required module github.com/microcosm-cc/bluemonday@v1.0.1 retracted by module author: Retract older versions as only latest is to be depended upon

# summary
Suggested version: v0.36.3

gocompat says:

HEAD is now at a0349afb Release v0.36.2
Switched to branch 'release-v036'
Your branch is up to date with 'origin/release-v036'.

Cutting a Release (and modifying non-markdown files)

This PR is modifying both version.json and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to release-v036. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

@MarcoPolo
Copy link
Collaborator

Let's merge on monday

@MarcoPolo MarcoPolo merged commit 921cc71 into release-v036 Sep 4, 2024
25 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants