Repository navigation
release: 2.4.4 bridge (Multi-Forge runtime, protocol 2 lifecycle artifact) - #183
Merged
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
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.
Refs #179. Version bump 2.4.3 -> 2.4.4 across the sources of truth (
VERSION,ainative.__version__, bothAGENTS.mdstack-version headers, README/README.fr/UPDATING/RELEASING/operator-guide/pilot pins, CHANGELOG section).scripts/check_release_versions.py --tag v2.4.4passes locally.This is the V2 bridge release: it carries the full Multi-Forge runtime (credential confinement, forward-protocol detection ->
CLI_UPDATE_REQUIRED, features/State V2, provider-neutral workflow + claims, Release V3 consumer, fail-closed source resolver, provider-aware diagnostics) while its lifecycle artifact deliberately remains protocol 2 (ainative-lifecycle-v2-2.4.4.zip), so current runtimes can consume it. The protocol-aware bridge gate reports the gate as explicitly not applicable for this publication.Also included: an env-hygiene fix in
tests/test_lifecycle_update_transport.py— some tests setAINATIVE_UPDATE_URL/tokens directly and left them in the process; a following suite in the same interpreter inherited a surprise selector (reproduced locally, fixed by restoring the environment insetUp).After merge: tag
v2.4.4on the exact merge SHA, watchRelease assetsto completion, verify assets + digests + provenance, runscripts/check_bridge_release.py --bridge-version 2.4.4against the published release, then set the repository variableV3_BRIDGE_RELEASE=2.4.4.