Repository navigation
ci: run all publishing workflow tests - #20
Merged
Merged
Conversation
nichinichisou0609
marked this pull request as ready for review
October 9, 2026 11:33
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.
PR and main CI now discover all tests in
.github/scripts, including the music-data, compression, refresh, prebuilt-publication, and JP network helper tests. They run alongside the existing story, catalog, and recognition tests using the current Python matrix and dependencies.The Python 3.13 job also checks the configured publishing consumer using Node 22 and the existing sparse checkout of the Player songs modules. A configured consumer requires Node.js, both modules, and the aptitude API; local runs can leave
MUSIC_DATA_PAGEunset.Validation: actionlint and CI on Python 3.11–3.14 passed. The Python 3.13 workflow-test step completed with 356 passed and 4 skipped, including both Player consumer tests. The remaining optional tests require music-data samples or ONNX Runtime.