cannwork-rehearsal 0.3.0 → 0.3.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.
- package/README.md +9 -1
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -65,6 +65,14 @@ Start the app in watch mode:
|
|
|
65
65
|
bun dev
|
|
66
66
|
```
|
|
67
67
|
|
|
68
|
+
## Credentials and login
|
|
69
|
+
|
|
70
|
+
- The access token stays in process memory only and is never written to `~/.cannwork-tui/cannwork.json`.
|
|
71
|
+
- The refresh token is encrypted with AES-256-GCM using a key derived from a stable machine fingerprint, then stored as `refreshTokenEnc`; `refreshTokenSavedAt` records when it was written and is metadata only.
|
|
72
|
+
- **Breaking upgrade:** on first launch after upgrading from a version that stored plaintext tokens, the legacy `accessToken`, `refreshToken` and `accessTokenExpiresAt` fields are deleted and you must log in again with `/login` or `/gitcode-token`.
|
|
73
|
+
- If the machine fingerprint changes (host identity or OS user), the stored refresh token can no longer be decrypted and you need to log in again.
|
|
74
|
+
- Multi-instance refreshes are serialized through a SQLite lease lock (`token_refresh_lock`). If the local database is unavailable, the launcher falls back to best-effort refreshes.
|
|
75
|
+
|
|
68
76
|
## Scripts
|
|
69
77
|
|
|
70
78
|
| Script | Description |
|
|
@@ -87,7 +95,7 @@ Releases are published manually to <https://registry.npmjs.org/> in two phases:
|
|
|
87
95
|
|
|
88
96
|
### Phase 1 — unscoped trial release (kept live)
|
|
89
97
|
|
|
90
|
-
1. Set `name` to `cannwork-rehearsal` and `version` to `0.
|
|
98
|
+
1. Set `name` to `cannwork-rehearsal` and `version` to `0.3.1` in the root `package.json` (single source of truth).
|
|
91
99
|
2. `npm login` (any account with publish rights).
|
|
92
100
|
3. `bun run release` — runs typecheck + tests, cross-compiles, then publishes the 5 platform packages followed by the main package. Add `--dry-run` to pack and verify without uploading.
|
|
93
101
|
4. Check each package on the registry (`npm view <pkg> version`). A `0.0.0-stage` value means npm staged the version for review; wait for it to go live (or approve it on npmjs.com) before smoke-testing.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "cannwork-rehearsal",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.2",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"bin": {
|
|
6
6
|
"cannwork": "bin/cannwork.js"
|
|
@@ -10,11 +10,11 @@
|
|
|
10
10
|
"README.md"
|
|
11
11
|
],
|
|
12
12
|
"optionalDependencies": {
|
|
13
|
-
"cannwork-rehearsal-win32-x64": "0.3.
|
|
14
|
-
"cannwork-rehearsal-linux-x64": "0.3.
|
|
15
|
-
"cannwork-rehearsal-linux-arm64": "0.3.
|
|
16
|
-
"cannwork-rehearsal-darwin-x64": "0.3.
|
|
17
|
-
"cannwork-rehearsal-darwin-arm64": "0.3.
|
|
13
|
+
"cannwork-rehearsal-win32-x64": "0.3.2",
|
|
14
|
+
"cannwork-rehearsal-linux-x64": "0.3.2",
|
|
15
|
+
"cannwork-rehearsal-linux-arm64": "0.3.2",
|
|
16
|
+
"cannwork-rehearsal-darwin-x64": "0.3.2",
|
|
17
|
+
"cannwork-rehearsal-darwin-arm64": "0.3.2"
|
|
18
18
|
},
|
|
19
19
|
"publishConfig": {
|
|
20
20
|
"registry": "https://registry.npmjs.org/",
|