Release camunda-modeler v5.21.0

[github-actions]

What's inside?

https://github.com/camunda/camunda-modeler/blob/develop/CHANGELOG.md#unreleased

New Features:

• support Zeebe user task (#4087)
• improve camunda:historyTimeToLive (#4062)
• always display documentation and multi-instance field in Camunda 7 diagrams (bpmn-io/bpmn-js-element-templates#67, #4037)
• allow Boolean and Number types in Camunda 8 diagrams (bpmn-io/bpmn-js-element-templates#64, #3622)

Fixes:

• adjust FEEL parsing to accept certain broken expressions (camunda-modeler#4073)
• apply all chained conditional properties (bpmn-js-element-templates#49)
• hide output mappings unsupported for terminate end event (#4096)
• report secrets as warn, not error (camunda/bpmnlint-plugin-camunda-compat#157)

Release Checklist

To be done immediately after creating this issue.

• (optional) update release presentation page

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 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 master: git checkout master && git pull && git checkout develop && git merge master
• 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 master: git checkout master && 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

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
• close current milestone

[nikku]

Found during integration testing: #4181.

[nikku]

@marstamm Let's populate the "What's inside section" for future reference / to guide testing (#4067)?

[github-actions]

Created follow up release issue.

Assigned @barmac as the next release commander.