codecov[bot]
commented
4 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 95.79%. Comparing base (
c1bbab4) to head (db1d5e2). Report is 2 commits behind head on main.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #75 +/- ## ======================================= Coverage 95.79% 95.79% ======================================= Files 3 3 Lines 333 333 ======================================= Hits 319 319 Misses 14 14 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
v2.1.1->v3.0.0Release Notes
sigstore/gh-action-sigstore-python (sigstore/gh-action-sigstore-python)
### [`v3.0.0`](https://redirect.github.com/sigstore/gh-action-sigstore-python/releases/tag/v3.0.0) [Compare Source](https://redirect.github.com/sigstore/gh-action-sigstore-python/compare/v2.1.1...v3.0.0) ##### Added - `inputs` now allows recursive globbing with `**` ([#106](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/106)) ##### Removed - The following settings have been removed: `fulcio-url`, `rekor-url`, `ctfe`, `rekor-root-pubkey` ([#140](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/140)) - The following output settings have been removed: `signature`, `certificate`, `bundle` ([#146](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/146)) ##### Changed - `inputs` is now parsed according to POSIX shell lexing rules, improving the action's consistency when used with filenames containing whitespace or other significant characters ([#104](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/104)) - `inputs` is now optional *if* `release-signing-artifacts` is true *and* the action's event is a `release` event. In this case, the action takes no explicit inputs, but signs the source archives already attached to the associated release ([#110](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/110)) - The default suffix has changed from `.sigstore` to `.sigstore.json`, per Sigstore's client specification ([#140](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/140)) - `release-signing-artifacts` now defaults to `true` ([#142](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/142)) ##### Fixed - The `release-signing-artifacts` setting no longer causes a hard error when used under the incorrect event ([#103](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/103)) - Various deprecations present in `sigstore-python`'s 2.x series have been resolved ([#140](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/140)) - This workflow now supports CI runners that use PEP 668 to constrain global package prefixes ([#145](https://redirect.github.com/sigstore/gh-action-sigstore-python/pull/145))Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.