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

chore: update Release Please config for GA #295

Merged
merged 4 commits into from
May 16, 2024
Merged

Conversation

k3llymariee
Copy link
Contributor

@k3llymariee k3llymariee commented May 16, 2024

Updating the release please config to (hopefully) allow for a 1.0.0 release. Please let me know if I've missed anything! I probably did!

@@ -1,3 +1,3 @@
{
".": "0.13.0"
".": "1.0.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

is this right? we did already have a 1.0.0 at some point before so I'm not actually sure this will work

Copy link
Contributor

Choose a reason for hiding this comment

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

You can't update the manifest directly - it'll confuse release-please, since this is what records the existing version. Instead, you can add a ! to a PR/commit title.

Example: feat!: some feature that triggers the GA releases

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok cool wasn't sure!

Copy link
Contributor

Choose a reason for hiding this comment

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

(If you don't have any last minute changes that you can add the ! to, you can also do it on a previous PR. (this is something we do all the time in SDKs if we accidentally forgot something.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

cool i'm going to merge this one in soon, so maybe just this? #293

@k3llymariee k3llymariee merged commit 998d788 into main May 16, 2024
2 checks passed
@k3llymariee k3llymariee deleted the kelly/release-rdy branch May 16, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants