bump: tag and release v1.0.0

[shizhMSFT]

Release

This would mean tagging 80e3fc4 as v1.0.0 to release.

Vote

We need at least 4 approvals from 6 maintainers to release notation v1.0.0.

• Junjie Gao (@JeyJeyGao)
• Milind Gokarn (@gokarnm)
• Patrick Zheng (@Two-Hearts)
• Pritesh Bandi (@priteshbandi)
• Rakesh Gariganti (@rgnote)
• Shiwei Zhang (@shizhMSFT)

Changes

The code changes compared to v1.0.0-rc.7 include:

• fix(test): E2E test cases for OCI layout #692
• build(deps): Bump github.com/sirupsen/logrus from 1.9.2 to 1.9.3 #702
• fix: fix the issue with getting credentials for docker.io #703
• build(deps): Bump github.com/notaryproject/notation-go from 1.0.0-rc.3 to 1.0.0-rc.6 in /test/e2e/plugin #710
• fix: Updating documentation with AWS Plugin support #711
• fix: login and logout will leverage docker config and os default store #712
• chore: update issue templates #594
• bump: bump oras-credentials-go v0.2.0 #717
• build(deps): Bump golang.org/x/term from 0.8.0 to 0.9.0 #716
• fix(e2e): update testdata OCI layout images #727
• build(deps): Bump ossf/scorecard-action from 2.1.3 to 2.2.0 #724
• [StepSecurity] ci: Harden GitHub Actions for fixing Pinned-Dependencies #731
• [StepSecurity] ci: Harden GitHub Actions for fixing Token-Permissions #730
• build(deps): Bump oras.land/oras-go/v2 from 2.2.0 to 2.2.1 #735
• chore: add license header to files and github action workflow to check license #739
• build(deps): Bump golang.org/x/term from 0.9.0 to 0.10.0 #734
• build(deps): Bump actions/checkout from 3.0.2 to 3.5.3 #737
• build(deps): Bump actions/add-to-project from 0da8e46333d7b6e01d0e857452a1e99cb47be205 to edc057aef96b993afe5d68104418f68a536264aa #745
• build(deps): Bump github/codeql-action from 2.20.1 to 2.20.4 #742
• fix: unset NOTATION_USERNAME and NOTATION_PASSWORD to avoid leaking credentials to plugin #746
• feat: add trace for executables #744
• build(deps): Bump github.com/notaryproject/notation-core-go from 1.0.0-rc.4 to 1.0.0 #752
• build(deps): Bump github/codeql-action from 2.20.4 to 2.21.0 #751
• bump: upgrade notation-go to v1.0.0 #754
• doc: update README to align with the new brand name #750

Full Changelog: v1.0.0-rc.7...80e3fc4

Action Requested

Please respond LGTM (approve) or REJECT (request for changes).

[JeyJeyGao]

LGTM

[priteshbandi]

Should we do a dev build before 1.0 to do a round of sanity test?

[shizhMSFT]

Should we do a dev build before 1.0 to do a round of sanity test?

We have the build on the main branch passing (as well as this PR). Meanwhile, we have released v1.0.0-rc.7 that the release pipeline has no issue. Thus, I think we are fine to not have a dev build.

If you have concerns, we can enable the weekly dev release workflow and manually trigger the workflow to publish a dev release.

[Two-Hearts]

LGTM

[JeyJeyGao]

LGTM

[priteshbandi]

LGTM