@chrysb/alphaclaw 0.3.2-beta.4 → 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.
|
@@ -32,6 +32,24 @@ Changes committed ([abc1234](commit url)): <-- linked commit hash
|
|
|
32
32
|
• path/or/resource (new|edit|delete) — brief description
|
|
33
33
|
```
|
|
34
34
|
|
|
35
|
+
### Release Flow (Beta -> Production)
|
|
36
|
+
|
|
37
|
+
Use this release flow when promoting tested beta builds to production:
|
|
38
|
+
|
|
39
|
+
1. Ensure `main` is clean and synced, and tests pass.
|
|
40
|
+
2. Publish beta iterations as needed:
|
|
41
|
+
- `npm version prerelease --preid=beta`
|
|
42
|
+
- `git push && git push --tags`
|
|
43
|
+
- `npm publish --tag beta`
|
|
44
|
+
3. For beta template testing, pin exact beta in template `package.json` (for example `0.3.2-beta.4`) to avoid Docker layer cache reusing old installs.
|
|
45
|
+
4. When ready for production, publish a stable release version (for example `0.3.2`):
|
|
46
|
+
- `npm version 0.3.2`
|
|
47
|
+
- `git push && git push --tags`
|
|
48
|
+
- `npm publish` (publishes to `latest`)
|
|
49
|
+
5. Return templates to production channel:
|
|
50
|
+
- `@chrysb/alphaclaw: "latest"`
|
|
51
|
+
6. Optionally keep beta branch/tag flows active for next release cycle.
|
|
52
|
+
|
|
35
53
|
### Telegram Notice Format (AlphaClaw)
|
|
36
54
|
|
|
37
55
|
Use this format for any Telegram notices sent from AlphaClaw services (watchdog, system alerts, repair notices):
|