Notation v1.0.0-RC.5 is available!
The Notation maintainers are pleased to announce v1.0.0-RC.5 for notation CLI and notation-go library. This blog walks you through the major updates in this release.
Major updates in notation CLI and notation-go library
Notation is a CLI tool to sign and verify OCI artifacts. The v1.0.0-RC.5 changes include but are not limited to the following. See the v1.0.0-RC.5 release notes for details.
- Improve the output message for
notation inspect
andnotation list
when there is no signature associated with the image being referred - Update compatibility with the OCI distribution-spec 1.1.0-RC.2 and OCI image-spec v1.1.0-RC.3
- Use SHA256 instead of insecure SHA1 for certificate thumbprint in
notation inspect
- Update OCI image-spec from 1.1.0-RC.2 to 1.1.0-RC.3
Notation-go is a collection of Golang libraries to support signing and verifying OCI artifacts. It is based on the Notary Project signature specification. Notation-go v1.0.0-RC.5 removes OCI artifact manifest type from Sign function.
Deprecate flag --signature-manifest
in notation sign
Since v1.0.0-RC.5, Notation no longer supports creating signatures with OCI artifact manifest type in the signing process and deprecated the flag --signature-manifest
from notation sign
. Please note this is a breaking change in Notation v1.0.0-RC.5. We chose to make this deprecation before the v1.0.0 release due to the upstream changes in the OCI image-spec v1.1.0-rc.3 that removed the artifact manifest.
To mitigate the impact to Notation users, Notation v1.0.0-RC.5 is still able to read and verify the existing signatures stored with the OCI artifact manifest type in OCI v1.1.0-RC.1 compliant registries. OCI artifacts signed by earlier versions of Notation are still verifiable with Notation v1.0.0-RC.5.
Change default behavior and introduce a new flag --allow-referrers-api
Starting with Notation v1.0.0-RC.5 release, Notation will use the Referrers Tag Schema as the default behavior since most of the OCI registries are compatible with storing signatures using the Referrers Tag Schema. The Referrers API and its fallback strategy are still under development according to recent OCI Distribution Spec changes, so it is marked as experimental in Notation v1.0.0-RC.5.
In this context, Notation v1.0.0-RC.5 introduces a new experimental flag --allow-referrers-api
to the following commands:
- notation sign
- notation verify
- notation inspect
- notation list
Specifically, users need to set the environment variable NOTATION_EXPERIMENTAL=1
to enable this new flag, then Notation attempts the Referrers API and fallback to Referrers Tag Schema on failure when using with OCI registry. Otherwise, Notation has deterministic behavior and uses Referrers Tag Schema by default.
Please note that users need to add this experimental flag --allow-referrers-api
when verifying signatures with OCI v1.1 compliant registry after upgrading Notation from v1.0.0 RC.4.
Note
Referrers Tag Schema is described as<alg>-<ref>
, such as sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
. For backwards compatibility, this behavior should work in existing OCI v1.0 compliant registries without any changes needed.Credits
We would like to specially thank the Notary maintainers, contributors, and the broader Notary community for helping us throughout the release process with timely feedback, reviews, testing, and support to help ensure a timely release. Sending credits to the following contributors who made great contributions to v1.0.0-RC.5.
- @FeynmanZhou
- @iamsamirzon
- @JeyJeyGao
- @ningziwen
- @priteshbandi
- @shizhMSFT
- @Two-Hearts
- @toddysm
- @vaninrao10
- @yizha1
- @zr-msft
Download and give it a try
Follow this hands-on guide to get started.