3.x Release Procedure

mstenta · April 7, 2022, 6:45pm

Similarly, here is the standard procedure for releases of farmOS-map:

Confirm all dependencies are up-to-date (i.e. npm audit fix and create a commit with changes)
Create a “Release v[version]” commit (eg: Release v2.0.3 · farmOS/farmOS-map@6d25f8f · GitHub)
- Update CHANGELOG.md with new version and release date
- Update version in package.json (line 3) and package-lock.json (lines 3 and 9)
Tag new version (e.g. git tag v9000.0.1)
Push 2.x and tag to origin (e.g. git push --atomic origin HEAD:2.x v9000.0.1)
Update the farmOS-map library version in farmOS (line 10 and 13 of composer.libraries.json: farmOS/composer.libraries.json at 5c764c5b50f4d9404e7b20012d29a1f188506994 · farmOS/farmOS · GitHub)