Repository navigation
Refresh pinned actions and make release publication explicit - #47
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.
Update pinned checkout, artifact-upload and CodeQL actions to their verified upstream releases. PrivateMusic2’s native Rust workspace has no external crate dependencies.
Verification builds now upload artifacts without publishing a release on each main-branch push. Releases are created only from an explicit version tag or a manual run with create_release=true (default false), so publication stays the final step. PR builds still run, and duplicate branch-push builds are avoided.
Both workflow files parse successfully and whitespace checks pass. SwiftLint, native Rust tests, simulator/archive builds and CodeQL run through CI. No release or tag is created by this PR.
All active scanners, native tests, simulator tests and builds pass. The aggregate CodeQL status is neutral because the default branch retains an older C/C++ configuration; the current workflow already omits C/C++ since the remaining C implementations are excluded test oracles. This PR changes workflow files only, does not alter that pre-existing scope, and introduces no scanning alerts. No analysis history or scanning rule is removed.