Repository navigation
chore(release): 9.4.0 [skip-runtime-e2e] - #249
Merged
Merged
Conversation
Signed-off-by: Saurabh Jain <saurabh.jain@getaxonflow.com>
saurabhjain1592
force-pushed
the
release/prep-v9.4.0
branch
from
September 14, 2026 13:45
8a93095 to
d1a598d
Compare
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
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.
Release prep: the project version moves to 9.4.0 and the
[Unreleased]block is cut as[9.4.0]. One CHANGELOG gap is filled (below). No functional change.9.4.0 is a minor: additive, plus the deprecation of the simulation family and its
Asyncforms.getCategory()returning null for a category this SDK does not know, where the strict enum used to fail the whole read, is a fix;getCategoryValue()is new.Version sites moved
pom.xml<version>detectSdkVersion()reads from Maven's ownpom.propertiesThe
CHANGELOG.md[Unreleased]heading is renamed IN PLACE to[9.4.0]with today's date. It is a rename, never a heading inserted above: an inserted heading strands everything already merged beneath it, and the release workflows that publish from this file extract the block by exact heading.Verification
maven.compiler.source/targetwithmaven.compiler.releasein the SDK pom and five example poms, and wrote no CHANGELOG line. That is a property of the published jar:source/targetfix the language level and class-file version but leave javac linking against the running JDK's class library, so a Java 16+ API compiled clean on the PR board (JDK 17) and failed only on the JDK 11 lane. It is now an entry in the[9.4.0]Fixed section.Provenance
The release-prep procedure, for the current train. Every merged change since the last tag wrote its own CHANGELOG entry at merge time, so this PR cuts the block rather than composing it. The exceptions are named below.
Items not modified in this PR (with justification)
examples/pep-handshakeandexamples/typed-policiespin 9.3.0,examples/authzenpins 9.1.0, andexamples/basic,examples/explain-decision,examples/list-decisionsandexamples/wcp-retry-idempotencypin 9.0.0. They are CODE pins: Maven resolves them from Maven Central, where 9.4.0 does not exist until the operator publishes, so they move immediately after the publish, not here. They are listed individually because the spread (one to four releases behind) shows the post-publish sweep has been skipped for several cycles, which is worth fixing as its own change rather than hiding inside a release PR.examplesjob rewrites every example pom to the root pom's version before compiling. So the reason they must wait is Maven Central, not the board.For the operator, after the platform release
Nothing here is tagged, published or synced by this change. Once the platform release is live and this PR has merged:
Clients publish AFTER the platform, in that order: a published client for a platform that never shipped cannot be withdrawn.
Release notes for the GitHub release
The
[9.4.0]block ofCHANGELOG.md, verbatim.Skip-runtime-e2e justification
This pull request changes no behaviour. It moves the version sites this repository's release procedure names, and renames the CHANGELOG's
[Unreleased]heading in place to the released version. There is no new surface, no changed default, no changed fail direction, and nothing a runtime test could exercise that it does not already exercise at the previous version.The on-the-wire value is verified by reading it back from something other than the file that was edited, which is the check a runtime leg would perform: the compiled package for Go, the built jar's
pom.propertiesfor Java, the generated constant re-stamped and compared by sha256 for TypeScript, and the manifest-versus-literal pair each plugin's own CI gate already asserts. Those readbacks are in the Verification section above.Adding or updating a
runtime-e2e/test here would be an edit made to satisfy a gate rather than a demonstration of anything: the suites in this repository read the version from the package at run time, so they assert the same thing before and after this change.Approved by the operator on 2026-09-14T13:50Z: "Of course skip-runtime-e2e is fine on them and they should be merged - clearly no runtime e2e test makes sense for version change."