Workflow for releasing patch updates for older versions

[gfellerph]

At the moment, automated releases are only possible on the main branch. Older versions are supported with critical bugfixes for at least 6 month (?) after a new major version has been released. When switching to a new major version, a branch of the old version is being created (e.g. origin/release-v5). In order to release this branch automatically, the changeset workflow needs to be adapted.

Tasks

Beta Give feedback

1. Run the changeset release action on release/* branches as well, change release PR titles to include the release branch (e.g. chore(changesets): 🦋📦 publish packages (main, v5, ...))
2. Run documentation deployment actions on release/* branches as well

Issues:

• When releasing on older branches, the changelog on the main is not updated. The missing entries would need to be included in the right order manually
• The versions.json on the main branch would need to be updated manually

[gfellerph]

New plan

For testing: https://github.com/gfellerph/changeset-test/tree/main

[gfellerph]

Documented here https://github.com/swisspost/design-system/wiki/How-to-do-a-major-release. Automated implementation is too big of an investment for the return (and complexity added).