Repository navigation
Remove model release preparation and the unused catalogue pin - #242
Merged
Merged
Conversation
This was referenced Oct 5, 2026
This was referenced Oct 7, 2026
Open
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.
Part of #89
Removes model preparation from the release. Models were dropped from the release (#236) and the catalogue pin is signed by a lost test key, so models will come back later as their own signed publication.
unconfiguredand list no models, with no error.elastos publish-release.Net lines: +94 / -5,654 (-5,560), 27 files.
Local checks: publish-platform-artifacts-test.py OK; release-platform-input-test.py, prepare-release-platform-test.py and release-signer-test.py fail only on the same cases as develop when run on this Mac under /tmp (path permission and pinned interpreter checks); node --test check-product-data.test.mjs 84/84;
cargo test -p elastos-server --bin elastos -- publish::38/38;cargo test -p elastos-server --lib -- setup:: installed_release:: capsule_inventory:: release_publication:: carrier::417 passed, 1 failure that also fails on develop locally (media-tools ffmpeg parent permissions).