Skip to content

Conversation

@venetrius
Copy link
Member

@venetrius venetrius commented Dec 8, 2025

Related to: camunda/camunda-7-to-8-migration-tooling#454

Description

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.

@venetrius
Copy link
Member Author

venetrius commented Dec 8, 2025

Needs to be rebased (and maybe creating a new PR) once #7472 is merged.

Rebased on main

Base automatically changed from 415-productize-code-conversion-tool to main December 8, 2025 15:34
@venetrius venetrius force-pushed the migration-tooling-454 branch from c146ea2 to af0bc4a Compare December 8, 2025 15:41
@venetrius venetrius marked this pull request as ready for review December 8, 2025 15:46
@venetrius venetrius merged commit e2649bb into main Dec 8, 2025
14 checks passed
@venetrius venetrius deleted the migration-tooling-454 branch December 8, 2025 17:26
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.

3 participants