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.
deps(deps): bump the actions-updates group across 1 directory with 9 updates #97
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
base: main
Are you sure you want to change the base?
deps(deps): bump the actions-updates group across 1 directory with 9 updates #97
Changes from all commits
a37a8cbFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check warning on line 147 in .github/workflows/cd.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 147 in .github/workflows/cd.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 171 in .github/workflows/cd.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 171 in .github/workflows/cd.yml
Omitting "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 36 in .github/workflows/ci.yml
Omitting "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 36 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 72 in .github/workflows/ci.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 72 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 127 in .github/workflows/ci.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 127 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 128 in .github/workflows/ci.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 128 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 159 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 159 in .github/workflows/ci.yml
Omitting "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 196 in .github/workflows/ci.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 196 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 197 in .github/workflows/ci.yml
Omitting "--no-build" or "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Check warning on line 197 in .github/workflows/ci.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 219 in .github/workflows/ci.yml
Omitting "--ignore-scripts" allows lifecycle scripts to run during package installation.
Check warning on line 223 in .github/workflows/ci.yml
Define exact package version to avoid installing unverified releases.
Check warning on line 223 in .github/workflows/ci.yml
"npx" can install packages on-demand and run their lifecycle scripts.
Check warning on line 227 in .github/workflows/ci.yml
Define exact package version to avoid installing unverified releases.
Check warning on line 227 in .github/workflows/ci.yml
"npx" can install packages on-demand and run their lifecycle scripts.
Check warning on line 231 in .github/workflows/ci.yml
Define exact package version to avoid installing unverified releases.
Check warning on line 231 in .github/workflows/ci.yml
"npx" can install packages on-demand and run their lifecycle scripts.
Check warning on line 53 in .github/workflows/security.yml
Using dependencies without locking resolved versions is security-sensitive.
Check warning on line 53 in .github/workflows/security.yml
Omitting "--only-binary :all:" can lead to the execution of setup scripts. Make sure it is safe here.
Uh oh!
There was an error while loading. Please reload this page.