docs(deprecation): the platform removes the legacy policy routes in v12.0, not v11.1 - #251
Open
saurabhjain1592 wants to merge 2 commits into
Open
saurabhjain1592 wants to merge 2 commits into
saurabhjain1592 wants to merge 2 commits into
Conversation
…12.0, not v11.1 This corrects a shipped notice. The v11.0.0 platform stamps its legacy policy routes with X-AxonFlow-Removed-In: v11.1, and this SDK's deprecation notices, examples and tests repeated that release. The platform's removal release was then ruled to be 12.0.0 (a removal is a major change), and from v11.1.0 the platform sends X-AxonFlow-Removed-In: v12.0. Only the release named in text changes: doc comments, the README, examples, and the value the unit tests' mock platform sends and asserts. The SDK still reports whatever value the platform sends, so no code path changes. The runtime-e2e legs that read the header from a live platform now expect v12.0. They pass against a v11.1.0 platform and fail against a v11.0.0 one, so this change ships with the platform's v11.1.0 release. Signed-off-by: Saurabh Jain <saurabh.jain@getaxonflow.com>
…and v12.0 from v11.1.0 Signed-off-by: Saurabh Jain <saurabh.jain@getaxonflow.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
The platform's legacy policy routes are removed in v12.0, not v11.1. This PR changes that one release name everywhere this SDK states it.
The v11.0.0 platform stamps its deprecated legacy policy routes with
X-AxonFlow-Removed-In: v11.1. The removal release has since moved to 12.0.0, because a removal is a major change. From v11.1.0 the platform sendsX-AxonFlow-Removed-In: v12.0. The platform side is getaxonflow/axonflow-enterprise branchv12b/removal-release-restamp-v12-0.Only text and test fixtures change: doc comments, the README, examples, and the header value the unit tests' mock platform sends and asserts. The SDK reports whatever value the platform sends, so no code path changes.
Coupling: this lands with the platform's header change
runtime-e2e/read the header from a live platform and now expectv12.0. They fail against a v11.0.0 platform, which sendsv11.1, and pass against a v11.1.0 platform. That is expected, not a regression.5371bf3dd, merged 2026-09-21) restampsRemovalRelease = "v12.0"; the released v11.0.0 still sendsv11.1. HOLD for the release: the operator merges this with the v11.1.0 train.Local verification
mvn -o -Dtest=V11DeprecationsTest,V11ProvenanceTest testrc 0: 10 and 6 tests, 0 failures.Release notes