Skip to content

chore: prepare v0.2.2 manifest alignment and release notes (COD-476) #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shivros merged 1 commit into from
Sep 11, 2026
Merged

chore: prepare v0.2.2 manifest alignment and release notes (COD-476) #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ members = [
]

[workspace.package]
version = "0.1.0"
version = "0.2.2"
edition = "2024"
license = "MIT"
repository = "https://github.com/TechGodHQ/hydra"
Expand Down
23 changes: 23 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,29 @@ existed.
- **Selective projection** via `surfaces: [http, mcp]` allowlists, with CLI
command renames (`cli_command:`) when the public name should differ.

## Releases & versioning

**Status: v0.2.2 is proposed, not published.** The workspace manifests have been
aligned to `0.2.2` in preparation; no tag, GitHub release, or crates.io
publication exists yet. A separate task will publish it.

- **Historical tags are immutable.** Tags `v0.1.0` … `v0.2.1` were cut from
commits whose workspace manifests still said `0.1.0`; they are reproducible
git pins and will never be moved or rewritten. From v0.2.2 onward the
manifest version will agree with the tag at the moment of tagging.
- **What v0.2.2 covers:** merged PRs [#6](https://github.com/TechGodHQ/hydra/pull/6)
(DeepSec tracer example), [#7](https://github.com/TechGodHQ/hydra/pull/7)
(layered agent context), and [#8](https://github.com/TechGodHQ/hydra/pull/8)
(unary cursor pagination fixture) — release metadata, reference coverage,
and documentation/context changes. No production changes under `crates/*/src`.
- **Consumers pin git tags, not crates.io.** hydra is not published to
crates.io. Consumers pin a tag and regenerate:
`hydra-core = { git = "https://github.com/TechGodHQ/hydra", tag = "v0.2.2" }`
(same shape for `hydra-codegen`), then re-run
`cargo run -p hydra-codegen -- write` in their own repo and commit the
regenerated surfaces. Tag-pin examples become valid **only after the
v0.2.2 tag is actually published** — until then pin `v0.2.1`.

## License

MIT.
Loading