Release camunda-modeler v5.23.0

[github-actions]

What's inside?

General

• FEAT: build for arm64 on MacOS (#4238)
• FEAT: add basic auth for deployments to C8 self-managed (#4269)
• DEPS: update to @bpmn-io/[email protected]
• DEPS: update to @camunda/[email protected]
• DEPS: update to [email protected]
• DEPS: update to [email protected]
• DEPS: update to [email protected]
• DEPS: update to [email protected]
• DEPS: update to [email protected]

BPMN

• FEAT: remove background for embedded labels (bpmn-io/bpmn-js#2147)
• FEAT: add tooltip for Called decision group (bpmn-io/bpmn-js-properties-panel#1039)
• FEAT: make popup menu fully keyboard navigatable (bpmn-io/diagram-js#871)
• FEAT: do not scale context pad and popup menu by default (bpmn-io/diagram-js#883)
• FEAT: context pad position absolute instead of relative to element (bpmn-io/diagram-js#888)
• FIX: prevent infinite loop when applying conditional template (bpmn-io/bpmn-js-element-templates#78)
• FIX: preserve valid user input when changing element template (bpmn-io/bpmn-js-element-templates#86, #4249)
• FIX: mark non-object JSON as invalid example data (example-data-properties-provider#17)
• FIX: select participant when process ref lint error is selected (camunda/linting#104)

DMN

• FEAT: context pad position absolute instead of relative to element (bpmn-io/diagram-js#888)
• FEAT: do not scale context pad and popup menu by default (bpmn-io/diagram-js#883)
• FEAT: add support for implementing BKM as literal expression (bpmn-io/dmn-js#704, bpmn-io/dmn-js#826)
• FEAT: remove background for DRGElements (bpmn-io/dmn-js#855)
• FEAT: allow to provide accessible names to form fields (bpmn-io/dmn-js#843)
• FIX: add accessible names to multiple components (bpmn-io/dmn-js#843)
• FIX: improve contrast
• FIX: make table cells visible to screen readers (bpmn-io/dmn-js#821)

Forms

• FIX: prevent expressions from recomputing more than once (bpmn-io/form-js#1154)

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 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
• Update download page at Camunda.com with new MacOS links #4239
• 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
• close current milestone

[nikku]

Found during integration testing: #4289.

[philippfromme]

Screenshots will be updated shortly.

[github-actions]

Created follow up release issue.

Assigned @nikku as the next release commander.