Today the release process for Trivy Action is manual. This involves creating a new PR, alongside updating any tests for every Trivy release.

We can improve on this in the following way:

1. Fix the DB used with Trivy Action tests. This will make sure there are no differences observed in the results for the unit tests in Trivy Action.
2. Create a cross-repo trigger that triggers every time a new release of Trivy happens. Some investigation needs to happen to check how to obtain this. A starting point is discussed here https://github.com/orgs/community/discussions/26323
3. The trigger will prepare a version bump PR within the Trivy Action repo, which the maintainer can inspect and merge if all looks good.