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

release: 1.0.0-rc.1 #1684

Merged
merged 1 commit into from
Jan 9, 2025
Merged

release: 1.0.0-rc.1 #1684

merged 1 commit into from
Jan 9, 2025

Conversation

mistydemeo
Copy link
Contributor

This release contains the rename but no other content. Any remaining 1.0 content will come after the first prerelease.

@mistydemeo mistydemeo marked this pull request as ready for review January 8, 2025 20:53
@mistydemeo mistydemeo mentioned this pull request Jan 8, 2025
11 tasks
@ashleygwilliams
Copy link
Member

q- can we call this a release candidate? e.g. rc.1?

@mistydemeo
Copy link
Contributor Author

I think so. Let me double check our prerelease handling to make sure we'll correctly handle it like with the other naming scheme.

@mistydemeo
Copy link
Contributor Author

Yes, it should be fine. We'll handle .rc1 as a prerelease. I'll swap it over.

@mistydemeo mistydemeo changed the title release: 1.0.0-prerelease.1 release: 1.0.0-rc.1 Jan 9, 2025
@mistydemeo mistydemeo merged commit 09df520 into main Jan 9, 2025
32 checks passed
@mistydemeo mistydemeo deleted the release_1_0_0_rc1 branch January 9, 2025 21:05
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