Release camunda-modeler v5.24.0

[github-actions]

What's inside?

M77 issues, v5.23.0...develop.

• Camunda 7 quality of life improvements: Camunda Modeler 5.16 Task Inputparmeter Type List alphabetic sorted #3978, "Process name" field is duplicated #4317
• General (mdoeling) safety concern: Warn about missing BPMN Shape  #4277, Broken BPMN diagram (incomplete DI) blows up editor #4315
• Minor bugs: Bogus entries shown in tabs bar context menu #4181, On quitting with unsaved files, "cancel" should prevent following prompts to save #4186
• New modeling experience in Desktop Modeler - As a user I'm able to use the new context pad / improved canvas #4263
• placeholder support for element templates (Support placeholders in String and Text templates properties #4330, Support placeholder for properties (String, Text) bpmn-io/bpmn-js-element-templates#92, documentation

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
  • chore: update release info for v5.24.0 #4334

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)
  • Dependency updates (form-js, electron) #4333
• 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 ➡️ chore: update release info for v5.24.0 #4334
  • 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 - @nikku
  • Works on Mac - @barmac
  • Works on Windows - @marstamm
• 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
• close current milestone
• communicate closed support related issues to #ask-support

[nikku]

Issues identified during integration test:

• fix: allow accessing Desktop Modeler landing page camunda-docs#3892
• Minimap z-position is inconsistent  #4337
• New Context Pad is not repositioned on Properties panel move #4338
• Literal expression editor body has small hitbox #4342
• Missing modeling feedback when dropping data object onto participant #4345
• Selected field does not scroll into view #4346
• Bug or feature (?)
• ID duplicates reported after reloading editor #4347
• Boundary event attachment for compensation activity allowed via new context pad #4348
• "appendElement is not a registered action" with new context pad #4349
• Improve documentation for enabling/disabling feature flags #4350