release: v0.2.0 - #70
Merged
Merged
Conversation
|
| Filename | Overview |
|---|---|
| CHANGELOG.md | New file documenting v0.2.0 additions and changes; previously flagged issues (broken [#N] reference links, emoji prefixes) are resolved in this revision. Link definitions and date are correct. |
| Cargo.toml | Single-line workspace version bump from 0.1.0 to 0.2.0; all other workspace configuration is unchanged. |
| Cargo.lock | Auto-generated lock file reflecting the version bump across all seven workspace member crates; no dependency graph changes. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[GitWorkflow run\nstarts release] --> B[CHANGELOG.md\nauthor drafts v0.2.0 entries]
B --> C{PR #69:\nmanifest mismatch\nflagged}
C -->|Cargo.toml still 0.1.0| D[PR #70 this PR\nFix version + finalize changelog]
D --> E[Cargo.toml\n0.1.0 → 0.2.0]
D --> F[CHANGELOG.md\nAdded + Changed entries\nlink definitions]
D --> G[Cargo.lock\nseven crates synced\nto 0.2.0]
E & F & G --> H[cargo check --workspace\nclean]
H --> I[Merge PR #70]
I --> J[Tag v0.2.0\non squash commit]
Reviews (2): Last reviewed commit: "release: v0.2.0 (changelog + workspace v..." | Re-trigger Greptile
- Add CHANGELOG.md for 0.2.0 (Keep a Changelog format) covering the platform spine build-out: product seam, feature gating, Stripe webhooks, audit events, license sign/verify, auth, offline sync, migrations, and the security policy. Em-dash-free per the repo writing style. - Bump workspace version 0.1.0 -> 0.2.0 (inherited by all member crates via version.workspace = true) so the manifest, the changelog, and the v0.2.0 tag agree. Cargo.lock synced; cargo check clean. Supersedes the local-only changelog commit (fdbd410); lands via PR per the repo's PRs-into-main workflow.
AojdevStudio
force-pushed
the
release-0.2.0
branch
from
June 15, 2026 17:31
299d06c to
2f68fa5
Compare
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
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.
Lands the v0.2.0 CHANGELOG and aligns the workspace version, completing the release the GitWorkflow run started.
What's here
CHANGELOG.mdfor 0.2.0 (Keep a Changelog / SemVer), covering the full platform-spine build-out: product-module seam, feature gating, Stripe webhook ingestion, audit/event service, license sign/verify +/license/refresh, auth +/me, offline sync queue, SQLite migrations, the scoped gate registry, and the security policy. Written em-dash-free per the repo style.0.1.0→0.2.0in the rootCargo.toml(inherited by every member crate viaversion.workspace = true);Cargo.locksynced.Why
The changelog declared
## [0.2.0]and links toreleases/tag/v0.2.0, butCargo.tomlwas still0.1.0and no tag existed (the mismatch Greptile flagged on #69). This makes the manifest, changelog, and the upcomingv0.2.0tag agree.Verification
cargo check --workspaceclean at 0.2.0.fdbd410); landing via PR per the repo's PRs-into-main workflow.After merge: tag
v0.2.0on the squash commit.