feat: update release info to v5.31.0

[barmac]

Related to #4753

Proposed Changes

For suggestions:

  <ul className="dashed">
    <li>
      <h4>Element template runtime versions</h4>
      Define the runtime version for each element template to ensure compatibility with the Camunda runtime.
    </li>
    <li>
      <h4>Zeebe user task is now Camunda user task</h4>
      Implement user tasks as Camunda user tasks to ensure full compatibility.
    </li>
    <li>
      <h4>Improved FEEL support</h4>
      Access script task result expression easily thanks to context keys suggestions.
    </li>
    <li>
      <h4>Document preview component in Forms</h4>
      Model and view uploaded documents in a new preview component.
    </li>
    <li>
      <h4>Bug fixes and more</h4>
      This release includes bug fixes and additional minor improvements to enhance your experience.
    </li>
  </ul>

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[jarekdanielak]

Looks good 👍

[nikku]

Consider what we ship here:

• There is a clear path forward (Zeebe -> Camunda) user task first
• We now support you in the transition

I think this is not clearly reflected with the current phrase.

[barmac]

Another try:

<h4>Migration to Camunda user tasks</h4>
Implement user tasks managed by Camunda with guidance on the way.

[barmac]

Thanks @nikku for your suggestions. I merged them into the PR. Current:

[barmac]

I am merging this now but we can still adjust before the final release.
@Balazs-PM @crobbins215 @lmbateman

[lmbateman]

Sorry I missed this!

— Zeebe user task is now Camunda user task

Should “Zeebe user task” and “Camunda user task” either be plural or in quotes? I think since we're referring to the name of a type of object, quotes would make sense.

• Zeebe user tasks are now Camunda user tasks
• “Zeebe user task” is now “Camunda user task”

Also, do we need to specify full compatibility with what?

— Improved Camunda 8 editor intelligence
Editor intelligence now picks data provided by script tasks.

I’m not quite sure what this means. But if no one else is confused, the grammar seems fine. :)

[barmac]

Thanks for the feedback.

Regarding the user tasks, perhaps we can rewrite the message (#4763 (comment)). The changes in that area are:

• "Zeebe user task" got renamed to "Camunda user task"
• This is the preferred way of implementing user task.
• If you set the implementation to the other value, the application highlights this, and provides a message on deprecation.

I’m not quite sure what this means.

The improvement is about suggesting the nested properties from script result:

Screen.Recording.2024-12-19.at.11.55.32.mov

[lmbateman]

For the user task update, how about:
— “Zeebe user task” renamed to “Camunda user task”

Then the next sentence is fine, but could also be something like your second sentence, “Camunda user tasks are now the preferred implementation for all user tasks.”

Editor intelligence now picks data provided by script tasks.

Assuming I understand correctly, how about one of these?

• Nested properties are now provided in auto-complete results.
• Data provided by script tasks is now available in auto-completion.

If we want to stay with the original sentence, I would say “picks up” instead of “picks”, or perhaps use a different verb (sees? has access to?).

[barmac]

Thanks for the suggestions. Let's wait for feedback from the PMs, and we can adjust the release info after the winter holidays.

[crobbins215]

My suggestions

<h4>Enhanced FEEL support</h4>
Easily access script task result expressions with the help of context key suggestions.

<h4>Document preview component in Forms</h4>
Model and preview uploaded documents with the new document preview component.

<h4>Bug fixes and enhancements</h4>
 This release includes bug fixes and additional minor improvements to enhance your experience.