agent-dir 0.3.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +34 -0
- package/package.json +5 -2
package/README.md
CHANGED
|
@@ -340,6 +340,40 @@ POST /mcp
|
|
|
340
340
|
|
|
341
341
|
All HTTP endpoints are authenticated by default.
|
|
342
342
|
|
|
343
|
+
## Releases
|
|
344
|
+
|
|
345
|
+
Releases are automated with [semantic-release](https://github.com/semantic-release/semantic-release) from the `main` branch. Developers should **not** manually edit the version in `package.json` for normal releases.
|
|
346
|
+
|
|
347
|
+
Use [Conventional Commits](https://www.conventionalcommits.org/) for commits that should communicate release impact:
|
|
348
|
+
|
|
349
|
+
| Commit | Release |
|
|
350
|
+
| --- | --- |
|
|
351
|
+
| `fix: handle tunnel reconnect` | Patch (`0.3.0` → `0.3.1`) |
|
|
352
|
+
| `feat: add project snapshots` | Minor (`0.3.0` → `0.4.0`) |
|
|
353
|
+
| `feat!: change authentication protocol` | Major (`0.3.0` → `1.0.0`) |
|
|
354
|
+
| `feat: change API` with a `BREAKING CHANGE:` footer | Major |
|
|
355
|
+
| `docs:`, `test:`, `chore:`, `refactor:`, `ci:`, etc. | No release by default |
|
|
356
|
+
|
|
357
|
+
After a pull request is reviewed and merged into `main`, the release workflow runs the normal validation (`npm run check`, `npm test`, and `npm pack --dry-run`). If validation succeeds, semantic-release determines the next SemVer version from the Conventional Commit history, updates `package.json` and `package-lock.json`, creates the release commit, creates the `vX.Y.Z` Git tag, creates the GitHub Release, and publishes the package to npm.
|
|
358
|
+
|
|
359
|
+
The release commit is marked `[skip ci]`, so it does not start another release cycle. A push to `main` that contains no release-worthy Conventional Commit produces no release.
|
|
360
|
+
|
|
361
|
+
For an intentional breaking release, use the `!` marker on the commit type/scope or add a `BREAKING CHANGE:` footer, for example:
|
|
362
|
+
|
|
363
|
+
```text
|
|
364
|
+
feat!: change authentication protocol
|
|
365
|
+
```
|
|
366
|
+
|
|
367
|
+
or:
|
|
368
|
+
|
|
369
|
+
```text
|
|
370
|
+
feat: change authentication protocol
|
|
371
|
+
|
|
372
|
+
BREAKING CHANGE: clients must use the new authentication protocol
|
|
373
|
+
```
|
|
374
|
+
|
|
375
|
+
Do not use arbitrary keywords such as `bump` to control releases. The existing `v0.3.0` release is the baseline for this automation.
|
|
376
|
+
|
|
343
377
|
## Contributing
|
|
344
378
|
|
|
345
379
|
Contributions are welcome. See [CONTRIBUTING.md](.github/CONTRIBUTING.md) for development setup, testing requirements, MCP compatibility guidance, and pull-request expectations.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agent-dir",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"description": "Expose a local project to an AI agent through authenticated MCP, filesystem tools, and allowlisted development commands",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -29,11 +29,14 @@
|
|
|
29
29
|
"lint": "biome lint .",
|
|
30
30
|
"check": "biome check . && tsc --noEmit",
|
|
31
31
|
"check:write": "biome check --write --unsafe .",
|
|
32
|
-
"prepublishOnly": "npm run check && npm test"
|
|
32
|
+
"prepublishOnly": "npm run check && npm test",
|
|
33
|
+
"release": "semantic-release"
|
|
33
34
|
},
|
|
34
35
|
"devDependencies": {
|
|
35
36
|
"@biomejs/biome": "^2.5.15",
|
|
37
|
+
"@semantic-release/git": "^11.0.1",
|
|
36
38
|
"@types/node": "^24.19.1",
|
|
39
|
+
"semantic-release": "^25.0.9",
|
|
37
40
|
"typescript": "^7.0.2"
|
|
38
41
|
},
|
|
39
42
|
"keywords": [
|