Skip to content

Conversation

@megglos
Copy link
Contributor

@megglos megglos commented Jan 16, 2026

Description

Align spec with this recent fix camunda/camunda#43909

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)

PR Checklist

  • My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
  • My changes are for an already released minor and are in a /versioned_docs directory.

@megglos megglos force-pushed the meg-update-8-8-spec branch from bc17a8d to ec9f187 Compare January 16, 2026 08:42
@github-actions
Copy link
Contributor

👋 🤖 🤔 Hello, @megglos! Did you make your changes in all the right places?

These files were changed only in versioned_docs/version-8.8/. You might want to duplicate these changes in docs/.

  • versioned_docs/version-8.8/apis-tools/orchestration-cluster-api-rest/specifications/correlate-message.api.mdx

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

Copy link
Member

@tmetzke tmetzke left a comment

Choose a reason for hiding this comment

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

👍 Thanks, @megglos

@megglos megglos merged commit 467a747 into main Jan 16, 2026
7 checks passed
@megglos megglos deleted the meg-update-8-8-spec branch January 16, 2026 09:24
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