Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prep for v1.0.0 release #73

Merged
merged 1 commit into from
Nov 19, 2021
Merged

Conversation

jdolitsky
Copy link
Contributor

  • Update Go modules
  • Update GitHub Actions to watch v1 branch
  • Remove stability warning from README

- Update Go modules
- Update GitHub Actions to watch v1 branch
- Remove stability warning from README

Signed-off-by: Josh Dolitsky <josh@dolit.ski>
@sajayantony
Copy link
Contributor

@jdolitsky - Thank you for making this release happen.

@shizhMSFT
Copy link
Contributor

@jdolitsky Recently, I've learnt that we can use GITHUB_TOKEN to do release instead of using our own PAT.

I've updated for notaryproject/notation#135. Do you want to also apply that to oras and oras-go?

Copy link
Contributor

@shizhMSFT shizhMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@shizhMSFT shizhMSFT added the v1 Things belongs to version 1.x label Nov 19, 2021
@jdolitsky
Copy link
Contributor Author

@shizhMSFT - I think yes, absolutely, for releases with binaries.

In this case, since Go modules uses git, I will just create the tag

@jdolitsky jdolitsky merged commit f423508 into oras-project:v1 Nov 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1 Things belongs to version 1.x
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants