Repository navigation
Refresh pinned Selenium workflow actions - #55
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.
Updates the six GitHub Actions dependencies proposed by Dependabot PR #54 to their latest official releases, pinned by immutable upstream release commit SHA:
actions/setup-nodev7.1.0actions/setup-javav6.1.0actions/download-artifactv8.0.2actions/cachev6.1.0actions/deploy-pagesv5.0.1actions/github-scriptv9.0.0This updates 22 action references in the current
mainbranch and changes no framework or test behavior. It also gives the repository's required browser matrix a normal same-repository PR context: Dependabot PR #54 fails before browser tests because GitHub does not expose the protectedAPP_PASSWORDsecret to Dependabot. The required full checks remain enabled and must pass before merge.Local validation:
git diff --checkpassed.The current local machine does not provide Java 21, so Maven validation was not run locally; hosted required checks are authoritative for the exact PR head.