@uiid/bertrand 0.10.0 → 0.11.0
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 +11 -0
- package/dist/bertrand.js +244 -4476
- package/dist/run-screen.js +594 -48549
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -195,6 +195,17 @@ bun run db:migrate # Apply migrations to ~/.bertrand/bertrand.db
|
|
|
195
195
|
|
|
196
196
|
The dashboard has its own `tsc -b` typecheck — run from `dashboard/`.
|
|
197
197
|
|
|
198
|
+
## Releasing
|
|
199
|
+
|
|
200
|
+
Releases are driven by [release-please](https://github.com/googleapis/release-please) from conventional commits on `main`.
|
|
201
|
+
|
|
202
|
+
1. Land commits in conventional format (`feat:`, `fix:`, `refactor:`, etc.). Hidden types — `chore`, `docs`, `test`, `ci` — don't trigger a release.
|
|
203
|
+
2. The `Release Please` workflow opens or updates a release PR with the next version + `CHANGELOG.md` entries.
|
|
204
|
+
3. Merging the release PR creates the git tag and a GitHub Release.
|
|
205
|
+
4. The same workflow then publishes to npm with provenance (typecheck + tests run first).
|
|
206
|
+
|
|
207
|
+
The `.release-please-manifest.json` file tracks the last released version; release-please updates it automatically. Publishing relies on the `NPM_TOKEN` repo secret (npm Automation token).
|
|
208
|
+
|
|
198
209
|
## License
|
|
199
210
|
|
|
200
211
|
MIT
|