Release Camunda Modeler v3.5.0

[nikku]

Release Camunda Modeler v3.5.0

What is inside

• Numerous DMN (decision table + DRD) bug fixes
• dmn-js updated to latest diagram-js foundation (Fix DRD not working with diagram-js@4 bpmn-io/dmn-js#412)
• inverse connections for all toolkits (Add ability to swap source and target on connect and reconnect bpmn-io/diagram-js#386)
• Some BPMN bug fixes
• Deployment: Make it a repetitive action
• Saving authentication details (Remember authentication details with endpoint configuration #1067)
• Sub-Processes are not collapsible anymore (Remove the ability to model collapsed sub-processes #1486)
• Supporting Camunda 7.12

Prerequisites

• mark table-js as compatible with diagram-js@6 and release patch release @philippfromme
• mark bpmn-js-properties-panel as compatible with bpmn-js@6 @pinussilvestrus
• release bpmn-js-properties-panel minor @pinussilvestrus
• release diagram-js major
• release bpmn-js major
• release [email protected] minor
• mark cmmn-js-properties-panel as compatible with [email protected]
• release cmmn-js-properties-panel
• integrate table-js@latest and diagram-js@latest into dmn-js
• release [email protected] => pending releases of dmn-js-decision-table, dmn-js-literal-expression, and dmn-js
• publish updated versions of utility libraries, marked as compatible with latest libs
• integrate into Camunda Modeler:
  • bpmn-js-properties-panel@latest
  • dmn-js-properties-panel@latest
  • cmmn-js-properties-panel@latest
  • diagram-js@latest
  • dmn-js@latest
  • cmmn-js@latest
  • bpmn-js@latest
  • ...

Checklist

• put up code freeze appointment in calendar (include modeling, qa, sre, and Team-Support)
• make sure dependencies are released (rm -rf node_modules && npm i && npm run all works)
  • bpmn-js, dmn-js, cmmn-js, *-properties-panel, *-moddle, ...
• close all issues which are solved by dependency updates
• verify develop is up to date with master: git checkout master && git pull && git checkout develop && git merge master
• smoke test to verify all diagrams can be created
• update CHANGELOG
• semantic release (npm run release), cf. release schema
• merge to master: git checkout master && git merge develop
• wait for Travis to build the release
• execute integration test on released artifacts
  • Works on Linux @philippfromme
  • Works on Mac @barmac @oguzeroglu
  • Works on Windows @philippfromme
• trigger QA for fuzzy testing
• write blog post for blog.camunda.org, do not publish until released version is available for download on camunda.org
• publish release on Github Releases
• trigger mirroring of release to https://camunda.org/release/camunda-modeler/ via Jenkins
• update download version of Camunda Modeler at camunda.com
• publish blog post on blog.camunda.org
• spread the word
  • send release notice email
  • tweet
• close current milestone

[nikku]

Found during integration testing:

• BPMN Group not being correctly colored BPMN Group is not being colored #1598
• Participant connect feedback not being cleaned up Hover feedback not cleaned up when connecting to participant #1599
• DRD connection docking cannot be updated DRD element connection docking cannot be updated #1601
• DRD connections not being properly cropped DMN elements not correctly being cropped in DRD editor #1600
• DRD connection preview does not reflect final result DRD connection preview does not reflect actual result #1602
• DRD connection jumps on re-connect Connection jumps when reconnecting in DRD editor  #1603

It seems as if there is a more general issue in dmn-js-drd that we need to investigate.

The following issues seem to be regressions from our v3.4.1 release: #1599, #1601, #1600, #1602, #1603.

[nikku]

Additional issues found during testing:

• DRD append does not work anymore DRD append does not work anymore #1604
• Connections cannot be moved with DRD elements Selections with connections cannot be moved anymore #1605
• Reconnection DRD connections serializes invalid original="[object Object]" property Reconnecting DRD connections results in original=[Object] elements serialized in XML #1606

All of these seem to be regressions from our v3.4.1 release.

[barmac]

I can reproduce #1600 in Camunda Modeler 3.4.1, so it seems to not be a regression.