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(main): release 0.2.1 #452

Merged
merged 1 commit into from
May 28, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

0.2.1 (2024-05-28)

Bug Fixes


This PR was generated with Release Please. See documentation.

Copy link
Contributor

@fengelniederhammer fengelniederhammer left a comment

Choose a reason for hiding this comment

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

Let's wait for #451

@fengelniederhammer fengelniederhammer merged commit 2cc9ee9 into main May 28, 2024
@fengelniederhammer fengelniederhammer deleted the release-please--branches--main branch May 28, 2024 10:17
Copy link
Contributor Author

@pflanze
Copy link
Contributor

pflanze commented May 28, 2024

That's where maybe making a branch is appropriate (like v0.2). Then the revert can be kept off the main branch. The main branch is then to be released as 0.3 without any double reverting, and the v0.2 branch has the revert and the new 0.2.1 tag.

@fengelniederhammer
Copy link
Contributor

Sure, that makes sense. But then you end up with a much more complicated release model (more initial implementation effort, more maintenance effort, more coordination overhead). I'd like to avoid that as long as we can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants