Release camunda-modeler v5.29.0

[github-actions]

What's inside?

CHANGELOG, v5.28.0...develop, milestoned tasks

General

• FEAT: support Camunda 8.7 and 7.23 (#4610)
• FEAT: populate empty tab values from available create options (#4575)
• FEAT: allow plug-ins to contribute custom file types (#4568)
• FEAT: support Camunda 8 FEEL built-ins (bpmn-io/feel-editor#62)
• FIX: improve validation of first-item FEEL rule (bpmn-io/dmn-js#894)

BPMN

• FEAT: add Camunda 8.7 and 7.23 linter configurations (camunda/bpmnlint-plugin-camunda-compat#176)
• FEAT: lint user tasks to be implemented as Zeebe user tasks starting with Camunda 8.7 (camunda/bpmnlint-plugin-camunda-compat#179)
• FIX: lint message end events for task definition (camunda/bpmnlint-plugin-camunda-compat#180)
• FIX: correct broken styles after loading variable outline (#4555)
• FIX: show lint errors for FEEL expressions used in BPMN processes (camunda/bpmnlint-plugin-camunda-compat#175)
• FIX: search result highlight (#4538)
• FIX: do not change zoom when search openes (bpmn-io/diagram-js#931)
• FIX: prevent search from shifting down the canvas (#4547)

DMN

• FIX: display parameterless functions suggestion correctly (bpmn-io/dmn-js#898)
• FIX: variable name changes when element name/label changes (bpmn-io/dmn-js#863)
• FIX: make literal expression editor hitbox bigger in BKM (#4545)
• FIX: make literal expression variables table styles explicit (#4550)

Forms

• FEAT: implement filepicker component (bpmn-io/form-js#1264)
• FIX: align drag preview/sticker properly (bpmn-io/form-js#1267)
• FIX: adjust the am/pm time placeholder to hh:mm -- (bpmn-io/form-js#1289)
• FIX: do not create a simple label in datetime components (bpmn-io/form-js#1292)

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: add v5.29.0 release info #4643

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 ➡️ chore: add v5.29.0 release info #4643
  • 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
• close current milestone

To be done as a post-release activity.

• update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
  • camunda-docs-static
    • feat: Desktop Modeler v5.29.0 screenshots camunda-docs-static#507
  • camunda-docs-manual
    • feat: screenshots for Desktop Modeler v5.29.0 camunda-docs-manual#1693
  • camunda-docs
    • feat: update screenshots for Desktop Modeler v5.29.0 camunda-docs#4548
• provide content to the release presentation and notice
• trigger downloads page update via marketing request form
• add new version to update server releases
  • https://github.com/camunda/camunda-modeler-update-server/pull/161
• (optional) update supported environments page
  • Add new supported macOS version for Desktop Modeler camunda-docs#4590

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

• publish release via update server (push to live)
  • https://github.com/camunda/camunda-modeler-update-server/pull/162
• announce the release via the Camunda internal #c8-release-announcements channel
• communicate closed support related issues to #ask-support

[jarekdanielak]

Problems found during testing

• Form Editor crashes when FEEL expression is created in the File Picker form element #4644
• Forms compatibility does not show supported version #4646
• Modeler creates invalid Job Worker type user task #4648
• File drop shown when moving popup editor #4652

[jarekdanielak]

All release activities are complete.

[github-actions]

Created follow up release issue.

Assigned @abdul99ahad as the next release commander.