Repository navigation
fix(release): align Archive publication metadata - #200
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.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.
Align repository, installer and package URLs with this repository's current owner,
NDDev-Technocracy-Archive. The nine generated files differ only in the current owner spelling, including its lowercase container namespace. Repository identity, setup content, protocol behavior and component version0.0.94are preserved.The maintained renderer passed its full gate and deterministic seven-tree generation. The proposed tree was compared with current public main: no files were added or removed, and every changed byte belongs to the current-owner replacement. Existing version identity and public-output checks passed. This PR requires its own exact-head public CI before merge.
This source update creates no release tag or package publication. Compatible released ai-stp readers and registry publisher qualification precede new artifact publication. Existing releases and signatures remain immutable; revert and regenerate metadata before publication if needed, then fix forward afterward.