-
-
Notifications
You must be signed in to change notification settings - Fork 383
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
🎉 Release 2.8.0 #4304
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blocked by woodpecker-ci/plugin-ready-release-go#226
-> #4328 |
We should probably add a @pat-s As you are organizing the 3.0 release, is there anything else we should think of for 2.8? |
Not necessarily, as long as there aren't any (hidden) breaking changes ;) |
This comment was marked as off-topic.
This comment was marked as off-topic.
@anbraten I'm ready to release if you are |
Apart from that it's ready from my side as well. |
-> #4469 |
Tearing down https://woodpecker-ci-woodpecker-pr-4304.surge.sh |
@6543 Don't forget the migration notes |
@anbraten yould you add them? |
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 |
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 torelease/v2.8
this pull-request will be updated.Options
2.8.0 - 2024-11-28
🔒 Security
✨ Features
🐛 Bug Fixes
📈 Enhancement
secrets
in favor offrom_secret
[#4360]Misc