Repository navigation
Support Forge 1.x and 2.x release builds - #9
Merged
Merged
Conversation
Document and validate Forge compatibility lines before release publication.
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.
Support existing annotated tags for both Forge release lines, with exact source version, locked Forge/Dora dependencies and selected-branch ancestry validation. Preserve current target-branch implementation and dependency fixes; update separate English/Chinese README guidance.
BREAKING CHANGE: Forge 2.x deployments must align Forge libraries, nodes and Dora 1.x. Maintain Forge 1.x / Dora 0.4.x on stable/1.x.
Validation:
Publication requires the existing immutable annotated tag and tag-based build. Existing published tags/assets are not overwritten. Hardware, sustained-run and rollback acceptance and subsequent GitLab synchronization remain pending. Full commands/YAML/process logs are retained in the migration workspace; no missing-prerequisite diagnostic is counted as a compatibility pass.