@trailkeep/cli 0.3.1 → 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/.claude-plugin/plugin.json +1 -1
- package/README.md +5 -3
- package/bin/trailkeep +1 -1
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "trailkeep",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.2",
|
|
4
4
|
"description": "Injects your private repo notes and the current branch's effort file at session start, plus the effort skill.",
|
|
5
5
|
"author": { "name": "Mario Širić" },
|
|
6
6
|
"repository": "https://github.com/msiric/trailkeep",
|
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ It's a single POSIX shell script that needs only `git`. It never changes your re
|
|
|
10
10
|
npm install -g @trailkeep/cli && trailkeep install
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
Or without npm:
|
|
13
|
+
Or without npm, or if your npm goes through a company mirror that doesn't carry the package (a 404 from a feed proxy):
|
|
14
14
|
|
|
15
15
|
```sh
|
|
16
16
|
git clone https://github.com/msiric/trailkeep ~/.trailkeep && ~/.trailkeep/bin/trailkeep install
|
|
@@ -148,6 +148,8 @@ The workflow bumps the version in all three places, runs the tests, and only the
|
|
|
148
148
|
|
|
149
149
|
From a clone, `sh scripts/release patch` (or `X.Y.Z`) does the bump, tests, commit and tag locally and pushes; the tag starts the same workflow, which checks the versions, tests again and publishes. Either way, no machine but GitHub's talks to npm.
|
|
150
150
|
|
|
151
|
-
npm authentication
|
|
151
|
+
npm authentication:
|
|
152
152
|
- **Trusted publishing (preferred):** on npmjs.com, open the package's Settings, then Trusted Publisher, then GitHub Actions. Enter owner `msiric`, repository `trailkeep`, workflow `release.yml`. No secret is needed. npm only offers this for packages that already exist.
|
|
153
|
-
- **An `NPM_TOKEN` repository secret
|
|
153
|
+
- **An `NPM_TOKEN` repository secret** was used for the very first publish only. The workflow no longer reads it; trusted publishing is set up for `@trailkeep/cli`.
|
|
154
|
+
|
|
155
|
+
If a publish fails after the release commit and tag were pushed, run the workflow again with that exact version (`-f version=X.Y.Z`); it publishes the existing tag without bumping.
|
package/bin/trailkeep
CHANGED
package/package.json
CHANGED