Skip to content

Commit

Permalink
chore: release main (#5)
Browse files Browse the repository at this point in the history
🤖 I have created a release *beep* *boop*
---


<details><summary>1.1.1</summary>

##
[1.1.1](v1.1.0...v1.1.1)
(2024-06-20)


### Bug Fixes

* [SRE-826] add correct parenthesize syntax
([#4](#4))
([1428772](1428772))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

[SRE-826]:
https://stord.atlassian.net/browse/SRE-826?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
  • Loading branch information
stord-engineering-account authored Jun 20, 2024
1 parent 1428772 commit 7d45514
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "1.1.0"
".": "1.1.1"
}
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [1.1.1](https://github.com/stordco/actions-trivy/compare/v1.1.0...v1.1.1) (2024-06-20)


### Bug Fixes

* [SRE-826] add correct parenthesize syntax ([#4](https://github.com/stordco/actions-trivy/issues/4)) ([1428772](https://github.com/stordco/actions-trivy/commit/1428772ae7d226a73cd96991d92104a65c364ddb))

## [1.1.0](https://github.com/stordco/actions-trivy/compare/v1.0.0...v1.1.0) (2024-06-20)


Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ stordco/actions-trivy is used to run [trivy](https://github.com/aquasecurity/tri

```yaml
- name: Trivy scan in fs mode
uses: stordco/[email protected].0
uses: stordco/[email protected].1
with:
scan-type: 'fs'
github-token: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}
Expand Down

0 comments on commit 7d45514

Please sign in to comment.