f27303264f
The Discord release-notify workflow read the version from frontend/package.json but never wrote it back, so every merge to release announced the SAME version (the CHANGELOG ended up with two "[2.0.1]" entries). Now, after generating the CHANGELOG and before announcing, the workflow bumps the PATCH in frontend/package.json and commits it alongside the CHANGELOG to release. Each merge advances the counter: 3.0.0 -> 3.0.1 -> 3.0.2 ... Also sets the baseline to 3.0.0 so the next release is announced as v3.0.0. To jump the major/minor, edit frontend/package.json on the release branch (e.g. "version": "3.1.0") and the next merge continues from there. |
||
|---|---|---|
| .. | ||
| actions-cache-cleanup.yml | ||
| backend-e2e-tests.yml | ||
| backend-unit-tests.yml | ||
| build-espidf-toolchain.yml | ||
| discord-issues.yml | ||
| discord-release-notify.yml | ||
| docker-publish.yml | ||
| frontend-tests.yml | ||
| library-compile.yml | ||
| test-circuit.yml | ||