Skip to content

Release 0.1.2 #36

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
forkrul merged 1 commit into from
Oct 17, 2026
Merged

Release 0.1.2 #36

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
5 changes: 4 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## [Unreleased]

## [0.1.2] - 2026-10-17

### Changed

- Pack hone's review into units of consecutive tasks up to ~400 changed lines instead of one unit per task, and after round 1 re-review only units not yet done: a unit is done after two consecutive clean reviews, and a fix re-opens every unit whose files it touches. Each round still logs a feature `- Rating:` line (the lowest unit rating), which smithy reads; the worked example's `code-review.md` shows the units ([#35](https://github.com/forkrul/damascus_development/pull/35))
Expand Down Expand Up @@ -80,6 +82,7 @@ _Initial release._
- Document the single-founder production-readiness plan ([#3](https://github.com/forkrul/damascus_development/pull/3))
- License the project under MIT; vendored submodules keep their upstream licenses ([#3](https://github.com/forkrul/damascus_development/pull/3))

[Unreleased]: https://github.com/forkrul/damascus_development/compare/v0.1.1...HEAD
[Unreleased]: https://github.com/forkrul/damascus_development/compare/v0.1.2...HEAD
[0.1.2]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.2
[0.1.1]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.1
[0.1.0]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.0
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,10 @@ From your repo root, pinning a release tag (see [Releases](https://github.com/fo

```bash
git submodule add https://github.com/forkrul/damascus_development.git vendor/damascus
git -C vendor/damascus checkout v0.1.1 # pin a release, never a moving branch
git -C vendor/damascus checkout v0.1.2 # pin a release, never a moving branch
git -C vendor/damascus submodule update --init --recursive # damascus's own pinned submodules
./vendor/damascus/install.sh
git add .gitmodules vendor/damascus && git commit -m "chore: vendor damascus v0.1.1"
git add .gitmodules vendor/damascus && git commit -m "chore: vendor damascus v0.1.2"
```

Then, in an agent session in that repo, start a feature with the orchestrator — in Claude Code, `/smithy` (or its alias `/spdd-pipeline`), or just say "let's build *feature X*" and ask for the smithy skill. Smithy runs the next stage, halts at every gate for your signoff, and picks up where it left off on `smithy --resume`. To see what a finished run looks like before starting one, read [`examples/`](examples/): one feature's complete artifact trail through all five gates.
Expand Down
Loading