Release camunda-modeler v5.25.0

[github-actions]

What's inside?

v4.9.0...develop
milestoned tasks

General

• CHORE: add accessible names to the XML/JSON editors (#4370)
• CHORE: set window title via HTML (#4376)
• CHORE: add accessible names to all inputs (#4367)
• CHORE: make privacy policy link sufficiently distinguishable (#4369)

BPMN

• FIX: do not show boundary event menu for compensation activities (#4348)
• FIX: allow deployment after initial save was cancled (#4370)
• FIX: do not suggest root elements in search (bpmn-js#2143)
• CHORE: make problem panel entries keyboard-focusable (#4368)
• CHORE: align template documentation link style (#4245)

DMN

• FEAT: add edit input/output button (bpmn-io/dmn-js#845)
• FIX: keep missing ID error (bpmn-io/dmn-js-properties-panel#85)

Forms

• FEAT: show link to field documentation in the properties panel (bpmn-io/form-js#1201)
• FIX: button labels properly evaluate expressions (bpmn-io/form-js#1181)
• FIX: ensure group paths are properly registered on add (bpmn-io/form-js#1173)

Release Checklist

To be done before the code freeze.

• inform QA about the release and its details so they can prepare for testing
• get in touch with the team (PM, UX and Engineering side), to clarify what topics will be included in the Release and their priority. Use this information to start preparing a concept for the blog post (see below) and release info (see below)
  • (optional) if possible, already create feature branch to update Release Info following our guidelines

To be done after code freeze to prepare and test the release.

• make sure changes in upstream libraries are merged and released
  • bpmn-js, dmn-js, *-properties-panel, *-moddle, camunda-bpmn-js, form-js, ...
• make sure potential new engine versions are available and marked correctly (alpha/stable)
• make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
• verify develop is up to date with main: git checkout main && git pull && git checkout develop && git merge main
• close all issues which are solved by dependency updates
• ensure that the modeler is free of major security vulnerabilities via npm audit
• smoke test to verify all diagrams can be created
• update Release Info
  • create a draft following our guidelines and based on priorities which were aligned with the team (PM, UX, and Engineering side)
  • create PR to merge the draft into develop. Assign to PM, UX and Engineering for review
• update CHANGELOG
• compile a list of blog worthy changes as input to release blog
• merge to main: git checkout main && git merge develop
• create release candidate (npm run release:rc -- [preminor|premajor|prerelease]), cf. release schema
  • wait for release build to create the artifacts
• execute integration test on released artifacts
  • Works on Linux
  • Works on Mac
  • Works on Windows
• notify QA about the release so they can test it

To be done to build the release after release testing completed.

• create release (npm run release), cf. release schema
  • wait for release build to create the artifacts

To be done once the release is built.

• publish release on Github Releases
• update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
  • camunda-docs-static
  • camunda-docs-manual
  • camunda-docs
• provide content to the release presentation and notice
• trigger downloads page update via marketing request form
• add new version to update server releases
• (optional) update supported environments page

To be done once release is publicly announced on release day.

• publish release via update server (push to live)
• announce the release via the Camunda internal #c8-release-announcements channel
• communicate closed support related issues to #ask-support
• close current milestone

[github-actions]

Created follow up release issue.

Assigned @jarekdanielak as the next release commander.