version_history.rst: jwt_authn change missed 1.10.0 #6684
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@larrywest can you fix the DCO? See https://github.com/envoyproxy/envoy/blob/master/CONTRIBUTING.md#fixing-dco . Fell free to squash the commits. |
|
ohhh... right... I think this might be because I did the commit directly on github rather than on my laptop. I'll follow those instructions. |
The PR (envoyproxy#6384) for the enhancement to jwt_authn was accepted before 1.10.0 was cut, and so the history was edited with 1.10.0 in mind, but the merge of happened just after 1.10.0 was cut. Therefore, this change moves the jwt_authn line from the "1.10.0 (April 5, 2019)" section to the "1.11.0 (Pending)" section. Signed-off-by: Larry West <Larry_West@intuit.com>
mpuncel
added a commit
to mpuncel/envoy
that referenced
this pull request
Apr 24, 2019
* master: docs: add extension policy (envoyproxy#6678) ext_authz: added ability to detect partial request body data (envoyproxy#6583) version_history.rst: jwt_authn change missed 1.10.0 (envoyproxy#6684) docs: fix link in pull request template (envoyproxy#6679) Explicitly convert absl::string_view to std::string. (envoyproxy#6687) docs: improving watermark docs/comments (envoyproxy#6683) http filter: add CSRF filter (envoyproxy#6470) event: reintroduce dispatcher stats (envoyproxy#6659) security: postmortem for CVE-2019-990[01] (envoyproxy#6597) Improve build rules for (test only) library quic_port_utils. (envoyproxy#6672) spell check: skip unsupported extensions when called with a file (envoyproxy#6648) Changed TestHooks to ListenerHooks (envoyproxy#6642) proto: move extension-specific linking validation into extensions (envoyproxy#6657) stats: add/test heterogenous set of StatNameStorage objects. (envoyproxy#6504) docs: move xds protocol to rst (envoyproxy#6670) fix version history order (envoyproxy#6671) Signed-off-by: Michael Puncel <mpuncel@squareup.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
The PR (#6384) for the enhancement to
jwt_authnwas accepted before 1.10.0 was cut, and so the history was edited with 1.10.0 in mind, but the merge happened just after 1.10.0 was cut.Therefore, this change moves the
jwt_authnline from the "1.10.0 (April 5, 2019)" section in "version_history.rst" to the "1.11.0 (Pending)" section.Risk Level: None - documentation only
Testing: Not applicable
Docs Changes: version_history.rst is the only file changed
Release Notes: (that's what is changed.)
Relates to issue #6355 and PR #6384