v0.60.0

Highlights

Remote Attestation State

Chainloop now supports a stateless attestation process #494.

This feature is disabled by default, to enable it you need to pass the --remote-state flag

$ chainloop att init --remote-state 
┌───────────────────┬──────────────────────────────────────┐
│ Initialized At    │ 12 Feb 24 15:50 UTC                  │
├───────────────────┼──────────────────────────────────────┤
│ Attestation ID    │ c8bac112-508c-4ab8-8ff2-9b7f22714628 │
│ Name              │ test                                 │
│ Team              │                                      │

This state of the attestation is being stored now in Chainloop!

Subsequently, to continue with the attestation process, the attestation ID, returned by the init process needs to be provided as well.

For example, to add materials, now:

$ chainloop att add --name artifact --value ./test.jar --remote-state --attestation-id c8bac112-508c-4ab8-8ff2-9b7f22714628
INF material added to attestation

The same applies to the reset or push methods.

What's Changed

• Bump Helm Chart Version => v0.56.0 by @github-actions in #482
• chore(deps): Bump CHAINLOOP_VERSION to use latest Chainloop CLI by @danlishka in #486
• chore(deps): Bump the anchore/sbom-action version by @danlishka in #485
• feat: release CLI as container image by @migmartri in #487
• chore(deps): Bump github.com/opencontainers/runc from 1.1.9 to 1.1.12 by @dependabot in #489
• chore(deps): Bump github.com/moby/moby from 24.0.5+incompatible to 24.0.9+incompatible by @dependabot in #490
• fix(authZ): propagate new policies across replicas by @migmartri in #484
• refactor(cli): modularize current state management code by @migmartri in #493
• chore(cli): make attestation cmds context aware by @migmartri in #497
• chore(api): move attestation API to common package by @migmartri in #496
• feat(api): remote attestation state API by @migmartri in #495
• feat(cli): remote attestation state support by @migmartri in #499

Full Changelog: v0.56.0...v0.60.0