Repository navigation
chore: upgrade github actions and fix workflow warnings - #53
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.
Summary
Existing workflows report Node.js action-runtime deprecation, missing Go cache dependency files, and Ubuntu runner migration warnings. Update the action versions and runner selection, and point Go caching at the server module.
Validation
3efac5b: documentation, Go server, and the complete macOS smoke job including Release tests (run). Documentation deployment and release workflows retain their existing triggers and are not exercised by the PR.CI reliability
The macOS job exposed an XCTest task-context crash and a timing-dependent share-rotation test. Run the MainActor credential-marker test asynchronously so its objects remain in XCTest’s async task context. Rotate the share at an explicit authenticated request boundary instead of using a 1.5 MB URI to delay routing. The regression still verifies file reads, uploads, old-token rejection, and new-token access across rotation.