release: v1.0.1 #3144
release: v1.0.1 #3144
Conversation
Xunzhuo
force-pushed
the
release-v1.0.1
branch
2 times, most recently
from
3d1199a to
2a255fe
Compare
release-notes/v1.0.1.yaml
Outdated
| - area: translator | ||
| change: | | ||
| Fixed nil secret in resourceversiontable | ||
| Fixed add missing http filters to the http filter chain |
There was a problem hiding this comment.
| Fixed add missing http filters to the http filter chain | |
| Add missing http filters to the http filter chain when ClientTrafficPolicy and MergeGateways is enabled |
|
can we just reuse doc from v1.0.0? |
@zirain can you elaborate ? |
there's little change around doc between v1.0.0 and v1.0.1, so should not create a new version of doc? |
Actually, it is reused from v1.0.0, just changed path and modified the related image tags in quickstart. We do not generate new paths for patch release, if we do so, there will be two paths for v1.0.0 and v1.0.1. |
| @@ -40,6 +40,7 @@ jobs: | |||
|
|
|||
| - name: Check links | |||
| run: make docs docs-check-links | |||
| continue-on-error: true | |||
There was a problem hiding this comment.
I think you can remove this now.
| @@ -43,7 +43,7 @@ unprivileged port, so that Envoy Gateway doesn't need additional privileges. | |||
| It's important to be aware of this mapping, since you may need to take it into | |||
| consideration when debugging. | |||
|
|
|||
| [`quickstart.yaml`]: https://github.com/envoyproxy/gateway/releases/download/v1.0.0/quickstart.yaml | |||
| [`quickstart.yaml`]: https://github.com/envoyproxy/gateway/releases/download/v1.0.1/quickstart.yaml | |||
There was a problem hiding this comment.
Some links are 404 as expected since release is not cut off yet
There was a problem hiding this comment.
this link will never 404, because github.com is ignored because of rate limiting.
Signed-off-by: bitliu <bitliu@tencent.com>
Signed-off-by: bitliu <bitliu@tencent.com>
Signed-off-by: bitliu <bitliu@tencent.com>
Signed-off-by: bitliu <bitliu@tencent.com>
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
release: v1.0.1