Repository navigation
chore(sdk): prepare 0.2.0rc2 - #112
Merged
Merged
Conversation
Advance the package version after the structured-error and reverse-tunnel policy fixes landed in develop. Publish a separate immutable RC so Hong Kong cluster regression can use the public package with adx-environment 0.1.0rc2. Keep the existing 0.2.0rc1 distributions unchanged. Signed-off-by: wayne <rcywjo@gmail.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
2 participants
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.
Prepare
akernel-sdk==0.2.0rc2after #108 merged intodevelop, so the structured-error and tunnel-policy fixes can be verified against the Hong Kong test cluster using a new public RC. This changes only the package version; existing rc1 artifacts remain immutable and the dependency staysadx-environment==0.1.0rc2.Validation:
make sdk-checkpassed (301 SDK unit tests, 35 benchmark-harness tests, Ruff and mypy). Wheel and sdist builds passed Twine checks; each installed in a separate environment outside the source tree with matching versions, isolated imports,pip checkand CLI smoke tests. Publication will use the existing prerelease/develop gate and PyPI Trusted Publishing after integration. Server-side Local/HostPath authorization remains tracked separately in #110.