search

sigstore / root-signing-staging

Staging TUF repository for Sigstore trust root
https://tuf-repo-cdn.sigstage.dev/
Apache License 2.0
3 stars 5 forks source link

build(deps): bump theupdateframework/tuf-on-ci from 0.9.0 to 0.10.0 #131

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps theupdateframework/tuf-on-ci from 0.9.0 to 0.10.0.

Release notes

Sourced from theupdateframework/tuf-on-ci's releases.

v0.10.0

Release includes several new features. It also fixes an issue with TUF keyids, see issue #292 (note that existing keyids are not automatically made compliant: tuf-on-ci-delegate --force-compliant-keyids can be used in a signing event to make that happen).

GitHub workflows require no changes (but you may want to add a .github/TUF_ON_CI_TEMPLATE/failure.md file, see below).

Changes

  • Artifact directories can now be up to 5 levels deep (#238)
  • actions: All action requirements are now version pinned (#248)
  • actions: .github/TUF_ON_CI_TEMPLATE/failure.md can now be used to define custom content for workflow failure issues (#270)
  • build-repository action: A human readable repository description is generated in index.html in the published metadata dir (#313)

Fixes

  • signer: keyid generation was fixed to be specification compliant (#294)
    • A feature was added to fix noncompliant keyids in repositories where they non-compliant keyids already present (#338)
  • test-repository action: Use a better default artifact-url (#275), handle a initial root in more cases (#346)
  • build-repository action: Delegation tree is now used to decide which metadata to include in published repo (#344)
  • tuf minimum dependency is now correctly set to 3.1 (#329)
Changelog

Sourced from theupdateframework/tuf-on-ci's changelog.

Changelog

Unreleased

v0.10.0

Release includes several new features. It also fixes an issue with TUF keyids, see issue #292 (note that existing keyids are not automatically made compliant: tuf-on-ci-delegate --force-compliant-keyids can be used in a signing event to make that happen).

GitHub workflows require no changes (but you may want to add a .github/TUF_ON_CI_TEMPLATE/failure.md file, see below).

Changes

  • Artifact directories can now be up to 5 levels deep (#238)
  • actions: All action requirements are now version pinned (#248)
  • actions: .github/TUF_ON_CI_TEMPLATE/failure.md can now be used to define custom content for workflow failure issues (#270)
  • build-repository action: A human readable repository description is generated in index.html in the published metadata dir (#313)

Fixes

  • signer: keyid generation was fixed to be specification compliant (#294)
    • A feature was added to fix noncompliant keyids in repositories where they non-compliant keyids already present (#338)
  • test-repository action: Use a better default artifact-url (#275), handle a initial root in more cases (#346)
  • build-repository action: Delegation tree is now used to decide which metadata to include in published repo (#344)
  • tuf minimum dependency is now correctly set to 3.1 (#329)

v0.9.0

GitHub Actions users are adviced to upgrade for safer dependency pinning that should avoid breakage in future.

Changes

  • actions: test-repository action has many additional features (#239)
  • actions: python package versions are now in logs again (#247)
  • signer: Improve signing robustness (#237)
  • Dependency updates (including more strictly pinned securesystemslib)

GitHub Actions upgrade instructions

A plain version bump from 0.8 works: Workflows require no changes.

... (truncated)

Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
jku commented 1 month ago

@kommendorkapten or @haydentherapper please have a look