Release camunda-modeler v5.20.0

[github-actions]

What's inside?

v5.19.0...develop, release milestone

General

• FEAT: allow users to re-open recently used files (#3917)
• FEAT: confirm on unsaved files before reload (#3886, #3240)
• FEAT: rework report feedback widget (#4086)
• FEAT: improve resizer and popup editor toggle interaction (#3895)
• FIX: correct user forum link (#4085)

BPMN

• FEAT: allow text annotations to overlap with the borders of subprocesses and pools (bpmn-io/bpmn-js#2049, #4035)
• FEAT: improve Camunda 7 variable events tooltip (#1016)
• FEAT: make FEEL error more forgiving (#3991)
• FEAT: display element template icon found in XML (bpmn-io/bpmn-js-properties-panel#1011)
• FEAT: align zeebe input propagation label and tooltip (bpmn-io/bpmn-js-properties-panel@5d8bd68, #4051)
• FEAT: word wrap FEEL expressions, textarea style (bpmn-io/properties-panel#319)
• FEAT: always show documentation field (bpmn-io/bpmn-js-element-templates#50, #4037)
• FEAT: validate Camunda 7 text area and select (bpmn-io/bpmn-js-element-templates#55)
• FEAT: ensure Camunda 8 user tasks have a form definition (camunda/bpmnlint-plugin-camunda-compat#151)
• FIX: support core replace in compensation behavior (bpmn-io/bpmn-js#2073, #4070)
• FIX: correct re-validation of entries when validator changes (bpmn-io/bpmn-js-properties-panel@e93e986, #3070)
• FIX: prevent infinite loop when suggesting variables (bpmn-io/variable-resolver#23)
• FIX: show scrollbars in popup editor (bpmn-io/properties-panel#319)

Forms

• FEAT: implement HTML component and cleanup Text component (bpmn-io/form-js#999)
• FIX: resize textarea on input changes (bpmn-io/form-js#1011)
• FIX: prevent demo data from being created on edited tables (bpmn-io/form-js#1005)

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 master: git checkout master && git pull && git checkout develop && git merge master
• 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 (feat(version-info): update to v5.20.0 #4101)
  • 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 (https://docs.google.com/document/d/157p4MHiZIXiTVTaZSp2_AlEwJ5yYO-XMR22_ogL4OXs/edit#heading=h.w6axwss3kj25)
• merge to master: git checkout master && git merge develop
• create release candidate (npm run release:rc -- [preminor|premajor|prerelease]), cf. release schema
  • wait for release build to create the artifacts (https://github.com/camunda/camunda-modeler/actions/runs/7797705671)
• execute integration test on released artifacts
  • Works on Linux @nikku
  • Works on Mac @barmac
  • 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.

• 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 (feat: update Desktop Modeler screenshots to v5.20.0 camunda-docs-static#435)
  • camunda-docs-manual (feat: update Desktop Modeler screenshots to v5.20.0 camunda-docs-manual#1598)
  • camunda-docs (feat(desktop-modeler): update screenshots to v5.20.0 camunda-docs#3299)
• provide content to the release presentation and notice (https://docs.google.com/presentation/d/1TPZ9dKnwYMi_XXz8ZWDLoGEZ1qwpDuurInT9ZjxbYEg/edit#slide=id.g2687119a2f4_0_5)
• trigger downloads page update via marketing request form
• add new version to update server releases (https://github.com/camunda/camunda-modeler-update-server/pull/142)

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: #4100

[nikku]

Found to not be fixed (yet): #3070.

[nikku]

Found during integration testing: #4105

[barmac]

Non-blocker: "Open recent file" displays new, unsaved diagrams as empty entries #4110

[barmac]

Non-blocker: Copy/Add cursor is displayed once I drag FEEL popup editor #4111

[barmac]

Critical regression: Properties panel crashes when file is closed with open FEEL popup editor #4112

[barmac]

Variable suggestions don't work in literal expression anymore: bpmn-io/dmn-js#785

[nikku]

https://github.com/camunda/camunda-docs-modeler-screenshots/issues/78 blocks generation of screenshots.

[nikku]

We're back! 🚋

[github-actions]

Created follow up release issue.

Assigned @marstamm as the next release commander.