@nettee/beacon 0.1.0 → 0.1.2

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.
Files changed (2) hide show
  1. package/README.md +24 -3
  2. package/package.json +2 -1
package/README.md CHANGED
@@ -138,9 +138,30 @@ same in-memory Gateway captures the quoted reply without contacting Feishu. It d
138
138
 
139
139
  ## Publishing
140
140
 
141
- Choose the next semantic version explicitly in `package.json` and
142
- `pnpm-lock.yaml`, then submit the release candidate through the normal pull
143
- request checks. After the initial package bootstrap, each push to `main` runs
141
+ Choose the next semantic version explicitly when the release requires a major
142
+ or minor bump, or when you want to override the automatic patch decision:
143
+
144
+ ```sh
145
+ pnpm bump-version major
146
+ pnpm bump-version minor
147
+ pnpm bump-version patch
148
+ ```
149
+
150
+ For an in-repository pull request that changes production CLI inputs under
151
+ `src/`, `package.json`, `pnpm-lock.yaml`, or `tsconfig.json` without changing
152
+ the package version, CI automatically commits a patch bump to the PR branch.
153
+ Test-only and documentation changes do not trigger a release. An explicit
154
+ version change takes precedence over the automatic patch bump, and CI rejects
155
+ a changed version that is not greater than the base branch version.
156
+
157
+ The bump job accepts only branches in this repository, not pull requests from
158
+ forks. It uses the job-scoped `github.token` to push the version commit, then
159
+ dispatches a fresh CI run for the new commit. This avoids a long-lived personal
160
+ access token while working around GitHub's suppression of workflows caused by
161
+ bot pushes.
162
+
163
+ Submit the release candidate through the normal pull request checks. After the
164
+ initial package bootstrap, each push to `main` runs
144
165
  the npm publish workflow. It verifies the source and packaged installation,
145
166
  publishes a version that is not yet present, and explicitly skips a version
146
167
  that already exists.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nettee/beacon",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "A single-host bridge from messaging and schedules to isolated agent runs",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -33,6 +33,7 @@
33
33
  },
34
34
  "scripts": {
35
35
  "build": "tsc -p tsconfig.json",
36
+ "bump-version": "node scripts/bump-version.mjs",
36
37
  "check": "biome check .",
37
38
  "dev": "tsx src/cli.ts",
38
39
  "e2e:message": "tsc -p tsconfig.e2e.json --noEmit && pnpm build && tsx --test e2e/message/*.e2e.test.ts",