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 2.8.0 #4304

Merged
merged 20 commits into from
Nov 28, 2024
Merged

🎉 Release 2.8.0 #4304

merged 20 commits into from
Nov 28, 2024

Conversation

woodpecker-bot
Copy link
Collaborator

@woodpecker-bot woodpecker-bot commented Nov 4, 2024

This PR was opened by the ready-release-go plugin. When you're ready to do a release, you can merge this pull-request and a new release with version 2.8.0 will be created automatically. If you're not ready to do a release yet, that's fine, whenever you add more changes to release/v2.8 this pull-request will be updated.

Options

  • Mark this version as a release candidate

2.8.0 - 2024-11-28

🔒 Security

✨ Features

🐛 Bug Fixes

📈 Enhancement

Misc

  • Use release-helper for release/* branches [#4302]

6543
6543 previously requested changes Nov 5, 2024
Copy link
Member

@6543 6543 left a comment

Choose a reason for hiding this comment

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

@woodpecker-bot woodpecker-bot changed the title 🎉 Release 2.7.3 🎉 Release 2.7.4 Nov 6, 2024
@6543
Copy link
Member

6543 commented Nov 6, 2024

-> #4328

@6543 6543 dismissed their stale review November 6, 2024 14:40

should be addressed

@woodpecker-bot woodpecker-bot changed the title 🎉 Release 2.7.4 🎉 Release 2.8.0 Nov 13, 2024
@6543 6543 added this to the 2.8.0 milestone Nov 21, 2024
@6543 6543 requested a review from anbraten November 25, 2024 20:38
@anbraten
Copy link
Member

We should probably add a 2.8.0 section to the migration section in docs before releasing and create the new docs version.

@pat-s As you are organizing the 3.0 release, is there anything else we should think of for 2.8?

@pat-s
Copy link
Contributor

pat-s commented Nov 25, 2024

Not necessarily, as long as there aren't any (hidden) breaking changes ;)
Thanks for asking.

@6543

This comment was marked as off-topic.

@6543
Copy link
Member

6543 commented Nov 27, 2024

@anbraten I'm ready to release if you are

@anbraten
Copy link
Member

We should probably add a 2.8.0 section to the migration section in docs before releasing and create the new docs version.

Apart from that it's ready from my side as well.

@6543
Copy link
Member

6543 commented Nov 27, 2024

-> #4469

@6543 6543 merged commit 985a5ae into release/v2.8 Nov 28, 2024
5 of 7 checks passed
@6543 6543 deleted the next-release/release/v2.8 branch November 28, 2024 18:50
@woodpecker-bot
Copy link
Collaborator Author

@anbraten
Copy link
Member

@6543 Don't forget the migration notes

@6543
Copy link
Member

6543 commented Nov 28, 2024

@anbraten yould you add them?

@6543
Copy link
Member

6543 commented Nov 28, 2024

I'm not sure what to write, It's just deprications the linter will already now show and the rest is non breaking those no docu needed

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.

4 participants