-
Notifications
You must be signed in to change notification settings - Fork 193
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
operate_8_2_6_support_notice #2245
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.
Thanks for taking this! As the events overlapped, let's already make clear 8.2.7 is available?
@megglos I'm going to accept your suggestions and give this a 👍 so we can merge this in quickly. |
Co-authored-by: Sebastian Bathke <sebastian.bathke@camunda.com>
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.
👍 will revisit if we need to clean up language/style, but let's merge this and get it released for awareness.
* Add initial and potential alpha 2 release note epics * Add Export activity endpoints * Remove 2126 * TW edits * Add document handling 2409 * Add 2073 unified deployment * Badges and edits * Remove license expiration 2529 placeholder * Add #2244 and #2245 * Remove 1314 Replay Scenarios * Add process instance migration * Remove release blog * Add Connectors entries * Add testing support for Connectors * Webhook connector details * Restructure connectors section * Add Gemini link
Description
Added text to the announcements section to warn users to not directly udpate from 8.1.x to 8.2.6.
When should this change go live?
asap
hold
label or convert to draft PR)?PR Checklist
/versioned_docs
directory, or they are not for an already released version./docs
directory (aka/next/
), or they are not for future versions.