ci: bump ansys/actions from 10.1.0 to 10.1.1 in the actions group #4230
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the actions group with 1 update: [ansys/actions](https://github.com/ansys/actions). Updates `ansys/actions` from 10.1.0 to 10.1.1 - [Release notes](https://github.com/ansys/actions/releases) - [Changelog](https://github.com/ansys/actions/blob/main/CHANGELOG.md) - [Commits](ansys/actions@v10.1.0...v10.1.1) --- updated-dependencies: - dependency-name: ansys/actions dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
maintenance
dependabot
bot
added
the
maintenance
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
| pull-requests: write | ||
| steps: | ||
| - uses: ansys/actions/doc-deploy-changelog@v10.1.0 | ||
| - uses: ansys/actions/doc-deploy-changelog@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| steps: | ||
| - name: Check pull-request name | ||
| uses: ansys/actions/check-pr-title@v10.1.0 | ||
| uses: ansys/actions/check-pr-title@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| steps: | ||
| - name: "Ansys documentation style checks" | ||
| uses: ansys/actions/doc-style@v10.1.0 | ||
| uses: ansys/actions/doc-style@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| - name: "Build wheelhouse and perform smoke test" | ||
| id: build-wheelhouse | ||
| uses: ansys/actions/build-wheelhouse@v10.1.0 | ||
| uses: ansys/actions/build-wheelhouse@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: ansys/actions/check-vulnerabilities@v10.1.0 | ||
| - uses: ansys/actions/check-vulnerabilities@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| steps: | ||
| - name: "Deploy the stable documentation" | ||
| uses: ansys/actions/doc-deploy-stable@v10.1.0 | ||
| uses: ansys/actions/doc-deploy-stable@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| steps: | ||
| - name: "Deploy the latest documentation" | ||
| uses: ansys/actions/doc-deploy-dev@v10.1.0 | ||
| uses: ansys/actions/doc-deploy-dev@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
|
|
||
| - name: "Perform versions cleanup - except certain tags" | ||
| uses: ansys/actions/hk-package-clean-untagged@v10.1.0 | ||
| uses: ansys/actions/hk-package-clean-untagged@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: ansys/actions/doc-changelog@v10.1.0 | ||
| - uses: ansys/actions/doc-changelog@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: ansys/actions/doc-deploy-pr@v10.1.0 | ||
| - uses: ansys/actions/doc-deploy-pr@v10.1.1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4230 +/- ##
==========================================
- Coverage 91.36% 91.22% -0.15%
==========================================
Files 193 193
Lines 15715 15715
==========================================
- Hits 14358 14336 -22
- Misses 1357 1379 +22 🚀 New features to boost your workflow:
|
Bumps the actions group with 1 update: ansys/actions.
Updates
ansys/actionsfrom 10.1.0 to 10.1.1Release notes
Sourced from ansys/actions's releases.
Commits
e0de7ddchore: updating CHANGELOG for v10.1.197b3ab0release: v10.1.17aeebd6docs: improve migration guide (#1003)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions