Release camunda-modeler v5.38.1

[Buckwich]

What's inside?

CHANGELOG

5.38.1

• DEPS: update to @camunda/linting@3.40.1
• DEPS: update to @bpmn-io/properties-panel@3.31.1

General

• FIX: revert inclusion of camunda builtin extensions due to performance issues (camunda/bpmnlint-plugin-camunda-compat#215)
• FIX: make priority-definition rule handle number value (camunda/bpmnlint-plugin-camunda-compat#213)
• FIX: template select button is now always visible (bpmn-io/properties-panel#436)

Release Checklist

• inform QA about the release and its details so they can prepare for testing

• (optional) if possible, already create a PR 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 the dependencies are updated in the Web Modeler
  • open a pull request with any necessary changes to integrate new libraries versions (https://github.com/camunda/web-modeler/pull/16439)
• 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
• [skip] compile a list of blog worthy changes as input to release blog
• [skip] merge to main: git checkout main && git merge develop
• create release candidate (npm run release:rc -- [preminor|premajor|prepatch]), cf. release schema
  • wait for release build to create the artifacts
  • (optional) to create further release candidates after the first one use npm run release:rc -- prerelease
• execute integration test on released artifacts
  • Works on Linux (@nikku)
  • Works on Mac (@Buckwich)
  • Works on Windows (@philippfromme)
• 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.

• communicate release with closed support-related issues to #ask-support (automated)
• publish release on Github Releases
• [skip] 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 (to be merged on release day) for:
  • camunda-docs-static (docs(desktop-modeler): update for v5.38.0 camunda-docs-static#589)
  • camunda-docs-manual (docs(desktop-modeler): update for v5.38.0 camunda-docs-manual#1809)
  • camunda-docs (docs(desktop-modeler): update for v5.38.0 camunda-docs#6384)
• provide content to the release presentation and notice
• trigger downloads pages (modeler & self-managed) update via marketing request form
• add new version to update server releases (https://github.com/camunda/camunda-modeler-update-server/pull/177)
• (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

[nikku]

This works, however I still see performance issues:

• With many FEEL expressions (Diagram editing with many FEEL expressions is slow #5219)
• With many element templates/connectors (Modeling is slow with connector templates enabled #5220)
• During copy and paste, related to minimap (Minimap causes performance issues #5215)