Repository navigation
ci: qualify ui on isolated OVH workers - #97
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
1 participant
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.
Run Linux package/browser qualification, result aggregation, advisory scans and publish safety on the isolated OVH CI pod. Download Chromium without a privileged OS package installer; the pod image supplies browser libraries.
The user explicitly approved retaining the single npm trusted-publishing apply job on a GitHub-hosted runner. npm currently does not support trusted publishing from self-hosted runners (https://docs.npmjs.com/trusted-publishers/). Publishing authentication and provenance remain unchanged; no token fallback was introduced.
Validation completed:
No npm publication or application dependency change was made.