Repository navigation
chore(release): publish Aleph 2.5.0 stable - #4
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
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.
Publish Aleph 2.5.0 as the official stable release with D Research 3.6.0 locked to its signed upstream tag and exact runtime projection. Package/validator versions, adapters, lockfiles, manifests and upgrade documentation are synchronized; causal drafting, review gates, simulation and roleplay algorithms are unchanged from the verified 2.5.0-rc.1 candidate.
Validation: the local 18-gate release suite passes; the final component pin is verified against the signed upstream Git tag and reproducible profile projection; downloaded source/assets are checked before publication. The exact source commit receives the required portable CI matrix before publication, and the release workflow builds both ZIPs twice, attests every asset and publishes the stable channel once. No independent live benchmark, empirical calibration or fixed browser memory saving is claimed.