Repository navigation
Support Forge 1.x and 2.x release builds - #4
Merged
Merged
Conversation
Document and validate Forge compatibility lines before release publication.
Update quinn-proto and quinn-udp to patched compatible versions in Cargo.lock; keep RustSec audit enabled.
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.
This change makes release builds select and validate the Forge compatibility line, immutable annotated tag, source ancestry, package version and locked Forge/Dora dependencies. It updates separate English and Chinese READMEs and adds release-boundary regression tests. Existing Ubuntu binary builders are reused where present; other nodes produce supported Python distributions/source archives. Node releases remain drafts, existing published assets/tags are not replaced, and node packages are not automatically published to PyPI. Core Forge retains its separate family-tag PyPI workflow with an explicit build-only mode.
Forge 2.x is a breaking change: deployments must align Forge libraries, nodes and Dora. Pending node migrations remain blocked by the release guard rather than being relabeled as 2.x.
Validation: 12 release-line tests and actionlint passed; supported wheel/sdist builds and distribution metadata checks passed. Core Forge additionally built all six package families on both lines. See
migration/release-lines-report.jsonfor this repository.Fresh
dora runsingle-node/Gateway-chain, Linux binary release, hardware/model/sustained-run and rollback acceptance were not performed for this release-tooling change and remain pending. No production publication or GitLab synchronization is included.