chore(release): bump version to 0.2.0 - #168
Merged
Merged
Conversation
First versioned release, and the first that the new GHCR publish workflow will turn into images. The Unreleased section removes two verticals (talent search, staff onboarding) and the xcrawl service and widens the sign-in allow-list on upgrade, so under SemVer this is a minor bump, not a patch; 1.0 would promise a stability the project is not claiming yet. 0.1.0 was never tagged and is not being tagged retroactively. Bumped everywhere the version is written: pyproject.toml and uv.lock, package.json and package-lock.json, and the two hardcoded strings behind the FastAPI app metadata and the /health response, so the running service reports the same number as the image tag. The changelog moves Unreleased under a dated 0.2.0 heading with compare links. After merge, tag the merge commit: `git tag v0.2.0 && git push origin v0.2.0` publishes 0.2.0, 0.2 and latest for both images. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MkhAyF5q6gKRHmRU9h5P6S
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The GHCR publish workflow from #167 is live, but the project has never been tagged and every version string still says
0.1.0. The firstvX.Y.Ztag needs a release commit behind it so the image tag,/health, and the changelog agree.Approach
Bump to
0.2.0everywhere the version is written:packages/core/pyproject.tomlanduv.lock,packages/ui/package.jsonandpackage-lock.json, and the two hardcoded strings inapi/main.pyandapi/models.py. The changelog's Unreleased section moves under[0.2.0] - 2026-09-22with compare links and a fresh empty Unreleased above it.Minor rather than patch because Unreleased removes two verticals and the xcrawl service and widens the sign-in allow-list on upgrade. Not
1.0.0because that promises a stability the project is not claiming yet.0.1.0was never tagged and is not being tagged retroactively.After merge, tag the merge commit to publish the images:
Checklist
pytest packages/core/tests/unit/) — no behavior change; health/version tests passruff checkandmypypass (make lint)cd packages/ui && npm run build) — version field only; lockfile validated🤖 Generated with Claude Code
https://claude.ai/code/session_01MkhAyF5q6gKRHmRU9h5P6S
Generated by Claude Code