Skip to content

Releases

For maintainers and contributors. How-to, with the gaps stated.

The project is a hackathon MVP. It has no automated release process, and there is no tagged release yet.

  • Version numbers. The backend (backend/pyproject.toml) and the web app (web/package.json) both say 0.1.0. The plan is 0.y.z while the project is young, with a v0.1.0 tag at the demo freeze.
  • Changelog. CHANGELOG.md at the repository root lists user-visible changes, newest first, kept by hand. The changelog page on this site is the same kind of list. There is no release automation.
  • Commits. Messages follow Conventional Commits with a scope from the list in CONTRIBUTING.md, for example fix(jobs): re-queue on lease expiry.
  • Deploys. infra/scripts/deploy.sh can deploy a git ref. Deploy a release tag rather than main. deploy.sh --rollback returns to the commit and images that ran before the last deploy. See deploy on AWS and back up, upgrade and migrate.
  • Docs. The docs site shows the date each page last changed, taken from git.

As of 20 October 2026, git tag --list shows no tag, and .github/workflows/ has no release workflow.

This is the manual process the repository supports. It is not automated.

  1. Make sure main is green on the five required checks. See tests.
  2. If the API changed, confirm backend/openapi/v1.json and the generated client are current.
  3. If dependencies changed, confirm THIRD_PARTY_NOTICES.md was updated.
  4. Move the user-visible items for the release in CHANGELOG.md under a dated heading, and say what changed in plain words.
  5. Raise the version in backend/pyproject.toml and web/package.json together. These are shared files and go through the integration owner.
  6. Tag the commit, for example git tag v0.1.0, and push the tag.
  7. To deploy that release, give its tag to the deploy script as described in deploy on AWS.

git tag --list shows the tag, and CHANGELOG.md has a heading for the release. After a deploy, the readiness check on the host passes, as the same page describes.

Next: project roadmap.

Map data © OpenStreetMap contributors, under the Open Database Licence. Code under the Apache-2.0 licence. Made by Yogesh.

Changeset Second Opinion is an independent open source tool for OpenStreetMap reviewers. It is not endorsed by, sponsored by or affiliated with the OpenStreetMap Foundation. OpenStreetMap is a trademark of the OpenStreetMap Foundation, used under itstrademark policy.