Skip to content

Commit 78183d5

Browse files
iso-harness 0.2.0, agentmd 0.3.0, monorepo adopts changesets
iso-harness 0.2.0: - New `validate` subcommand: schema-checks the iso/ source without writing anything. Exit 1 on errors, 0 on warnings/clean. - `build` now calls the validator first and refuses to fan out to the four target harnesses if mcp.json, config.json, or any agent/command frontmatter has schema errors (missing `command`, non-string env values, duplicate agent names, unknown-harness override keys, model that isn't a string, etc.). Warnings (empty description, empty body) are surfaced in the build summary but do not block. - 18 unit tests (was: 1 smoke-build script). agentmd 0.3.0: - New `--format sarif` on `lint` so findings upload to GitHub code scanning with the same dialect isolint emits. Driver name `agentmd`, rule IDs are the L-codes. Monorepo: - Adopt Changesets for version bumps + CHANGELOG generation. Existing tag-triggered release workflows still drive the npm publish; engineers add a changeset per PR, then `npm run version` bumps + commits + writes CHANGELOG.md, and a tag cut triggers the existing publish flow. - Root scripts: `changeset`, `changeset:status`, `version`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 7b502b0 commit 78183d5

17 files changed

Lines changed: 2034 additions & 30 deletions

File tree

.changeset/README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Changesets
2+
3+
Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
4+
with multi-package repos, or single-package repos to help you version and publish your code. You can
5+
find the full documentation for it [in our repository](https://github.com/changesets/changesets).
6+
7+
We have a quick list of common questions to get you started engaging with this project in
8+
[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md).

.changeset/config.json

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
{
2+
"$schema": "https://unpkg.com/@changesets/config@3.1.4/schema.json",
3+
"changelog": "@changesets/cli/changelog",
4+
"commit": false,
5+
"fixed": [],
6+
"linked": [],
7+
"access": "public",
8+
"baseBranch": "main",
9+
"updateInternalDependencies": "patch",
10+
"ignore": []
11+
}

README.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,31 @@ npm run build --workspace @razroo/isolint
8787
npm run test --workspace @razroo/agentmd
8888
```
8989

90+
## Releasing
91+
92+
Version bumps are driven by [Changesets](https://github.com/changesets/changesets).
93+
Every PR that changes a package should include a changeset describing the
94+
user-visible impact:
95+
96+
```bash
97+
npm run changeset # interactive — pick packages + bump level + summary
98+
npm run changeset:status # preview what the next `version` would do
99+
```
100+
101+
When you're ready to cut a release:
102+
103+
```bash
104+
npm run version # bumps package versions + writes CHANGELOG.md
105+
git commit -am "Version packages"
106+
git tag <pkg>-v<version> # e.g. agentmd-v0.3.0
107+
git push && git push --tags
108+
gh release create <pkg>-v<version> --generate-notes
109+
```
110+
111+
The tag-triggered release workflows in `.github/workflows/*-release.yml`
112+
take over from there — verify the tag matches `package.json`, run tests,
113+
build, and `npm publish --provenance`.
114+
90115
## End-to-end example
91116

92117
[`examples/pipeline/`](./examples/pipeline) is an executable demonstration

0 commit comments

Comments
 (0)