Release Camunda Modeler v5.8.0

[github-actions]

What's inside?

v5.7.0...develop, M61, CHANGELOG

General

• FIX: correctly deploy to Zeebe when extension missing in deployment name (#3432)
• FIX: correct reload shortcut (#3390)
• CHORE: log potentially invalid custom SSL certificates (#3411, #3415)
• DEPS: update to [email protected] (#3431)

BPMN

• FEAT: feature service and user tasks more prominently in replace menu (#1836)
• FEAT: integrate create + append anything (#1802, #1809, #1815, #1818, #1831, #1811, #1809, #1817)
• FEAT: simplify connection-multi icon (#1822, #2282)
• FEAT: join paths round by default (1827)
• FEAT: improved BPMN symbol rendering (#1830)
• FEAT: round connection corners (#1828)
• FEAT: support FEEL expressions in C8 error throw events (#3319)
• FEAT: support C8 escalation events (#3318)
• FEAT: improve editor support in C8 element templates for non FEEL languages (bpmn-io/bpmn-js-properties-panel#858)
• FEAT: autoresize name element in properties panel (bpmn-io/bpmn-js-properties-panel#705)
• FIX: serialize C8 templated properties in stable order (bpmn-io/bpmn-js-properties-panel#838)
• FIX: sort technical bindings in XML order (bpmn-io/bpmn-js-properties-panel#845, bpmn-io/bpmn-js-properties-panel#843, #3400)
• FIX: allow deletion of C8 extension properties on participant (#3417)
• FIX: allow C8 extension properties on all elements (#3365)
• FIX: correctly reset error when setting Message#correlationKey (#3392)
• DEPS: update to [email protected]
• DEPS: update to [email protected]
• DEPS: update to [email protected]
• DEPS: update to @camunda/[email protected]

DMN

• FEAT: set decision table header as title (bpmn-io/dmn-js#719)
• DEPS: update to [email protected]
• DEPS: update to [email protected]

Forms

• FEAT: add scalable palette component (bpmn-io/form-js#503)
• FEAT: support searchable selects (bpmn-io/form-js#381)
• FIX: correct various minor editing bugs (#3382, #3379, #3383, #3384, #3381, #3380, #3274)
• DEPS: update to [email protected]

Release Checklist

To be done immediately after creating this issue.

• add Slack role to release manager (@modeling-release-manager)
• (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)
• close all issues which are solved by dependency updates
• 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
• verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
• merge to master: git checkout master && git merge develop
• create release candidate (npm run release:rc -- --[prepatch|preminor|premajor]), 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 @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
• trigger mirroring of release to Camunda Download Center via Jenkins
• write blog post for the Camunda Blog, see guidelines ➡️ blog post
  • use the blog post template
  • add your contents to the newly created post
  • set yourself as the post author
  • share the post with your colleagues for review
  • share the post with #top-blog-submission for checkup and publishing ➡️ https://camunda.slack.com/archives/C03NMMN2R28/p1676030559379819
• update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
  • camunda-docs-static docs: update to Camunda Modeler 5.8 screenshots camunda-docs-static#331
  • camunda-docs-manual docs: update to Camunda Modeler v5.8.0 screenshots camunda-docs-manual#1399
  • camunda-docs-platform feat: update to Camunda Modeler 5.8.0 camunda-docs#1693
• provide content to the release presentation and notice
• request marketing to update the downloads page via request form
• add new version to update server releases ➡️ https://github.com/camunda/camunda-modeler-update-server/pull/113

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

• publish release via update server (push to live)
• close current milestone

[nikku]

Found: #3433

[nikku]

Release info:

[nikku]

I exhausively tested deployment / connection to a zeebe cluster:

• C8 SaaS
• C8 self-hosted (insecure)
• C8 self-hosted (secure, custom server certificate)

🟢

[barmac]

Found: #3435

[philippfromme]

Not a blocker, found: bpmn-io/form-js#539

[nikku]

Not a blocker: #3434

[barmac]

Not a blocker: #3436

[barmac]

Not a blocker: #3437

[barmac]

Not a blocker: #3438

[barmac]

A feature request but related to the release: #3439

[barmac]

Another feature request inspired by the release: #3440

[barmac]

[feature request] I guess this will be a good spring cleaning material: #3441

[barmac]

Regression: #3442

[nikku]

Not a blocker: #3443

[barmac]

[feature request] Another good spring cleaning issue: #3444

[nikku]

Confirmed: #1003

[barmac]

Not a big one: #3445

[nikku]

Found: #3446.

[barmac]

[feature-request] #3447

[barmac]

Super small bug: #3448

[barmac]

[feature-request] #3449

[philippfromme]

Found: #3450

[nikku]

Found: #3451.

[nikku]

Action required: Update screenshot generation utility to latest modeler release input[name='name'] changed to textarea[name='name'].

[nikku]

Action required: Update blog post publishing flow to latest version, provide internal release blog template.

[nikku]

Found: bpmn-io/bpmn-js#1840

[nikku]

Found: bpmn-io/bpmn-js#1839

[nikku]

Found: bpmn-io/bpmn-js-create-append-anything#4.

[nikku]

Found: bpmn-io/bpmn-js#1842.

[github-actions]

Created follow up release issue.

Assigned @marstamm as the next release commander.