notation icon indicating copy to clipboard operation
notation copied to clipboard

A CLI tool to sign and verify artifacts

Results 192 notation issues
Sort by recently updated
recently updated
newest added

As a user, I want to list the plugin(s) so that I can view the installed plugin(s) Implementation items to track: - [ ] https://github.com/notaryproject/notation/issues/230

enhancement
epic
User Story
triage

[Go 1.19](https://go.dev/blog/go1.19) is released with [release notes](https://go.dev/doc/go1.19)! It is time to bump up golang version to `1.19` by updating - `go. mod` - GitHub Actions

go
github_actions

CLI implementation for the tag to digest translation.

enhancement

Request by @priteshbandi in https://github.com/notaryproject/notation/issues/93 Instead of exporting types can we export routines so that underlying implementation can be changed without affecting callers? https://github.com/notaryproject/notation/pull/83#discussion_r709484002

enhancement
go

**Summary** Implementing sign command according to the spec #88 and #91 **Intended Outcome** `notation sign` command works as defined in the spec **Additional context**

Implement the new verify command to use the trust and policy store - [ ] https://github.com/notaryproject/notation/issues/216 - [ ] notation verify spec

**Summary** Implementing Notation directory structure according to the spec #167 **Intended Outcome** Notation directory structure works as defined by the spec **Additional context**

**Summary** CLI spec for notation inspect **Intended Outcome** CLI spec is defined for `notation inspect` command and related documents are updated accordingly **Additional context**

spec

As a user, I want to add/update/list/delete keys Implementation items to track: - [ ] https://github.com/notaryproject/notation/issues/226

enhancement
epic
User Story
triage

Need to decide what we'll do for RC1, and what we'll do post RC1 to help users easily add and remove certificates for verifications. The assumption is this would transition...