Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Correct Issue browser-actions/setup-chrome into release/1.13.x #19904

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #19876 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

The below text is copied from the body of the original PR.


This PR fixes the issue where the browser-actions/setup-chrome action would fail in the test-ui workflow job: https://github.com/hashicorp/vault/actions/runs/4575976373/jobs/8079513066

The problem was that an incorrect commit hash was being used. The proposed commit hash is the correct one and it was verified by temporarily removing the if condition on the test-ui job. This caused the job to execute in this branch: https://github.com/hashicorp/vault/actions/runs/4575747084/jobs/8078976210


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/marcboudreau/test-setup-chrome/initially-hopeful-piglet branch from 8295328 to f8714e1 Compare March 31, 2023 16:17
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/marcboudreau/test-setup-chrome/initially-hopeful-piglet branch from 3042d05 to 689f9c6 Compare March 31, 2023 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants