@oisin-ee/pi-dogsled 0.30.0 → 0.32.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
CHANGED
|
@@ -13,13 +13,13 @@ Install the binary on each Herdr host. Use the same release tag in each command.
|
|
|
13
13
|
Binary:
|
|
14
14
|
|
|
15
15
|
```sh
|
|
16
|
-
mise use github:oisin-ee/dogsled@v0.
|
|
16
|
+
mise use github:oisin-ee/dogsled@v0.32.0 # x-release-please-version
|
|
17
17
|
```
|
|
18
18
|
|
|
19
19
|
Pi (extension, tools, the `todo` tool, and skill), from npm:
|
|
20
20
|
|
|
21
21
|
```sh
|
|
22
|
-
pi install npm:@oisin-ee/pi-dogsled@0.
|
|
22
|
+
pi install npm:@oisin-ee/pi-dogsled@0.32.0 # x-release-please-version
|
|
23
23
|
```
|
|
24
24
|
|
|
25
25
|
At session start the extension compares its version with `dogsled --version` and warns when they differ.
|
|
@@ -49,6 +49,31 @@ herdr plugin install oisin-ee/dogsled --ref v0.28.0 --yes
|
|
|
49
49
|
|
|
50
50
|
The Claude and Codex plugins use the binary on `PATH`. The Herdr plugin's build step (`plugin/fetch.sh`) installs its own binary at `bin/dogsled`: the release archive for the manifest version, checked against its published SHA-256. When that release has no archive for the platform, it runs `cargo build --release --locked` instead, which needs Rust at the crate's `rust-version` or newer. A checksum mismatch stops the install. `DOGSLED_RELEASES` replaces the download base, such as a mirror. `herdr plugin link` skips build steps, so run `sh plugin/fetch.sh` in a linked checkout. No plugin starts host services.
|
|
51
51
|
|
|
52
|
+
## Releasing
|
|
53
|
+
|
|
54
|
+
Ordinary merges to `main` do not bump versions or publish packages.
|
|
55
|
+
Release-please maintains one release PR with lockstep versions and a changelog from conventional commits.
|
|
56
|
+
Every commit subject that reaches `main` must use conventional commits. For a squash merge, that subject is the PR title.
|
|
57
|
+
The bot uses `GITHUB_TOKEN`, so its release-PR updates do not start CI.
|
|
58
|
+
Nothing auto-merges the release PR.
|
|
59
|
+
|
|
60
|
+
When the user requests a release, merge the open release-please PR.
|
|
61
|
+
The merge runs the full CI suite through the reusable CI workflow.
|
|
62
|
+
After CI passes, the publish job creates `vX.Y.Z` at that release commit and dispatches dist.
|
|
63
|
+
Dist publishes the binaries and calls the existing npm publisher.
|
|
64
|
+
The publish job changes `autorelease: pending` to `autorelease: tagged` so release-please can prepare the next release.
|
|
65
|
+
|
|
66
|
+
If CI fails before tag creation, rerun the failed jobs at the same revision.
|
|
67
|
+
If dispatch fails after tag creation, dispatch the existing tag manually:
|
|
68
|
+
|
|
69
|
+
```sh
|
|
70
|
+
gh workflow run release.yml --ref vX.Y.Z -f tag=vX.Y.Z
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Never move an existing tag.
|
|
74
|
+
A partial publication can leave conflicting assets and requires review before a retry.
|
|
75
|
+
If dispatch failed before the label change, change the merged PR label from `autorelease: pending` to `autorelease: tagged` after dispatch succeeds.
|
|
76
|
+
|
|
52
77
|
## Web portal
|
|
53
78
|
|
|
54
79
|
Run the portal with `dogsled web`, then open `http://127.0.0.1:7465`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@oisin-ee/pi-dogsled",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.32.0",
|
|
4
4
|
"description": "Pi extension for dogsled: the board, the /dogsled panel, the inbox reader, and the dogsled tools. Needs the dogsled binary of the same version.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
1. Run the repository's heavy gate once, at the final revision. Limit it to the change if the task runner can do that. If a target fails, start a follow-up writer unit on the same branch with the failure. A finished writer is closed. When the fix arrives, run only the failed targets again.
|
|
4
4
|
2. Run `gh pr ready <n>`, then merge the PR. Then confirm that its state is `MERGED`.
|
|
5
|
-
3.
|
|
5
|
+
3. Landing never bumps versions or creates tags. Use conventional commit titles for feature PRs because release-please builds the changelog from them. Release only when the user asks: merge the open release-please PR. Its workflow runs the full CI suite, then tags the release commit and dispatches publication. Never auto-merge the release-please PR.
|
|
6
6
|
4. If GitHub Actions does not run because of billing, the local gate is the evidence. Say so once in the PR body.
|
|
7
7
|
5. Bring the local `main` up to date with `origin/main`. Leave the tree clean.
|
|
8
8
|
6. Report to the user what changed and what is live.
|