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

ci: Next release from main will be v4.0.0 #4044

Merged
merged 1 commit into from
Mar 22, 2022
Merged

ci: Next release from main will be v4.0.0 #4044

merged 1 commit into from
Mar 22, 2022

Conversation

joeyparrish
Copy link
Member

This release-please config file is a temporary measure until our first
automated feature release from main. So we have to explicitly state
the version number for this first release, and keep it up-to-date.

After the release, we should be able to remove this file and let the
workflow decide on version numbers automatically based on commit
messages.

This release-please config file is a temporary measure until our first
automated feature release from main.  So we have to explicitly state
the version number for this first release, and keep it up-to-date.

After the release, we should be able to remove this file and let the
workflow decide on version numbers automatically based on commit
messages.
@joeyparrish joeyparrish changed the title ci: Next release from master will be v4.0.0 ci: Next release from main will be v4.0.0 Mar 21, 2022
Copy link
Collaborator

@theodab theodab left a comment

Choose a reason for hiding this comment

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

Earlier, you said we might want to do a pass of old TODOs before we release v4.
Should we take a day to do that, or just do it at some point later?

@joeyparrish
Copy link
Member Author

We should do it before the release. I'm not merging the release PR just yet.

@joeyparrish joeyparrish merged commit 8cd42ca into shaka-project:main Mar 22, 2022
@joeyparrish joeyparrish deleted the release-please branch March 22, 2022 02:18
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants