Repository navigation
Reduce repeated release setup and superseded CI work - #6
Merged
Merged
Conversation
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.
Cross-platform release preparation previously used separate screenshot and preparation runners, repeated Qt/Python installation and tests, and committed the screenshot separately. It now prepares the version, renders the GUI, builds the manual and validates the final source in one job, producing one release-preparation commit. This removes one runner and one complete test pass per release while retaining parallel Windows/Linux builds and all existing checks.
CI now cancels superseded runs of the same workflow/ref, uses lightweight test requirements without PyInstaller, and keys dependency caches on application requirements as well as project metadata. Added bounded job timeouts and disabled redundant artifact compression for packaged outputs, with seven-day intermediate artifact retention. Release concurrency still keeps active releases running.
The preparation commit no longer rebases onto new, untested main changes after validation: a concurrent update safely fails the ordinary push instead. Legacy release and Zenodo workflows were inspected and left unchanged.
Validation: parsed all six workflow YAML files and checked job dependencies and Linux shell syntax; executed the updated preparation/version, offscreen screenshot, PDF generation and final validation steps locally in an isolated checkout. 34 cross-platform tests and 7 repository checks passed; source compilation and metadata/PDF checks passed. Windows/Linux packaged builds and full GitHub Actions execution still require remote runners.