Release camunda-modeler v5.28.0

[github-actions]

What's inside?

Changelog, v5.27.0...develop, milestoned tasks.

• FEAT: Use new built-in Camunda 8.6 functions (I can use the new built-in functions from Camunda 8.6 #4500)
• FEAT: Remove alpha tag from now stable engine profiles (Remove alpha tag from latest engine profile #4522)
• FEAT: Diagram search rework (Search improvements bpmn-io/diagram-js#913, Diagram search should only commit navigation changes on ENTER bpmn-io/bpmn-js#2189)
• FIX: Correct boolean type input elements in element template (Boolean type input elements throw output errors #4517)
• FIX: Lane label obscures during direct editing (Lane Label Obscures Text During Editing #4477)
• FIX: Version Tag binding bug fixes (Version tag binding input loses focus #4513, Version tag linting broken #4519)

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.28.0 release info #4540)

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
  • 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 (chore: add v5.28.0 release info #4540)
• 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
  • Sign release artifacts (Windows) @philippfromme

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. ➡️ https://github.com/camunda/camunda-docs-modeler-screenshots/actions/runs/11072959594/job/30768421161
  • Download artifacts and create PRs for:
    • camunda-docs-static (chore(get-started): bump screenshots to modeler v5.28.0 camunda-docs-static#492)
    • camunda-docs-manual (chore: bump Desktop Modeler screenshots to v5.28.0 camunda-docs-manual#1687)
    • camunda-docs (feat(desktop-modeler): update screenshots to v5.28.0 camunda-docs#4366)
• provide content to the release presentation and notice
• Provide content to 8.6 minor release notes (ref)
• trigger downloads page update via marketing request form
• add new version to update server releases (https://github.com/camunda/camunda-modeler-update-server/pull/158)
• (optional) update supported environments page

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

• publish release via update server (push to live) (ref)
• announce the release via the Camunda internal #c8-release-announcements channel ➡️ (ref)
• communicate closed support related issues to #ask-support ➡️ (ref)

[nikku]

Found during integration testing:

• Incorrect grammar error for nested date and time #4557
• Invalid FEEL expression error is not displayed in the problems panel for execution listeners #4562
• Accessing a FEEL expression [0] reports misleading message bpmn-io/bpmn-js-properties-panel#1078
• Indentation in XML/JSON view broken #4556
• deps: bump to @camunda/form-playground@0.16.1 #4558
• Parameterless functions are suggested with non-existing parameter #4539
• Welcome tab changes font size #4555
• Multi-element context pad is missing in DMN editor #4554
• chore: add forms section to changelog #4552
• Literal expression editor styles broken #4550
• Bottom panel gets empty when I switch from BPMN to DMN diagram with variables open #4546
• While decision overview is closed entering any value to the table/expression shifts the DMN diagram #4549
• Cannot easily drill down the collapsed subprocess as append element gets focussed  #4548
• Searching makes diagram shift down in the canvas #4547
• Parameterless functions are suggested with non-existing parameter #4539
• Improve search (make fuzzy again and more robust) bpmn-io/diagram-js#932, popup menu search broken (ref), unbuilt the feature
• Input field looses focus #4559

[barmac]

IMO "lint first item access" is a general feature as it's shared among all editors. So it does not belong to BPMN only.

[barmac]

@nikku #4542

[nikku]

Release candidate available for testing here.

[nikku]

Minor bump: We had to re-build the RC, due to a blocking issue discovered in pre-release testing / modeler integration.