memento-mori-jester 0.1.4 → 0.1.5
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 +2 -0
- package/docs/GETTING_STARTED.md +2 -0
- package/docs/RELEASE.md +6 -0
- package/docs/RELEASE_NOTES_v0.1.5.md +19 -0
- package/docs/TRUSTED_PUBLISHING.md +39 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -253,6 +253,8 @@ More setup examples:
|
|
|
253
253
|
- [Agent Setup](docs/AGENTS.md)
|
|
254
254
|
- [GitHub Actions](docs/GITHUB_ACTIONS.md)
|
|
255
255
|
- [Demo Script](docs/DEMO.md)
|
|
256
|
+
- [Roadmap](ROADMAP.md)
|
|
257
|
+
- [Trusted npm Publishing](docs/TRUSTED_PUBLISHING.md)
|
|
256
258
|
|
|
257
259
|
## Installer Scripts
|
|
258
260
|
|
package/docs/GETTING_STARTED.md
CHANGED
package/docs/RELEASE.md
CHANGED
|
@@ -13,6 +13,8 @@ npm publish
|
|
|
13
13
|
|
|
14
14
|
If npm asks for browser authentication, approve it in the browser window that opens.
|
|
15
15
|
|
|
16
|
+
For the less painful route, configure trusted publishing once using [TRUSTED_PUBLISHING.md](TRUSTED_PUBLISHING.md), then run the `npm Publish` workflow in GitHub Actions.
|
|
17
|
+
|
|
16
18
|
The package publishes these bins:
|
|
17
19
|
|
|
18
20
|
- `jester`: human CLI
|
|
@@ -93,3 +95,7 @@ npx -y memento-mori-jester@latest hook-status
|
|
|
93
95
|
```
|
|
94
96
|
|
|
95
97
|
Then stage a risky diff and confirm the hook blocks or cautions according to `hookFailOn`.
|
|
98
|
+
|
|
99
|
+
## 6. GitHub Release
|
|
100
|
+
|
|
101
|
+
Pushing a `v*` tag now creates a GitHub Release automatically. If `docs/RELEASE_NOTES_<tag>.md` exists, those notes are used; otherwise GitHub-generated notes are used.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# v0.1.5 Release Notes
|
|
2
|
+
|
|
3
|
+
This release makes the public release process feel more real and less manual.
|
|
4
|
+
|
|
5
|
+
## Added
|
|
6
|
+
|
|
7
|
+
- GitHub Release workflow for future `v*` tags.
|
|
8
|
+
- Manual npm trusted-publishing workflow, ready for npm's one-time trusted publisher setup.
|
|
9
|
+
- `ROADMAP.md` with near-term direction and product ideas.
|
|
10
|
+
- Trusted publishing setup guide.
|
|
11
|
+
|
|
12
|
+
## Why
|
|
13
|
+
|
|
14
|
+
The package is now live on npm, so the project needs a cleaner release path and a public roadmap. This release puts those pieces in the repo instead of leaving them as scattered instructions.
|
|
15
|
+
|
|
16
|
+
## Useful Links
|
|
17
|
+
|
|
18
|
+
- npm: https://www.npmjs.com/package/memento-mori-jester
|
|
19
|
+
- GitHub: https://github.com/Martin123132/Memento-Mori
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# Trusted npm Publishing
|
|
2
|
+
|
|
3
|
+
Trusted publishing lets GitHub Actions publish this package to npm without a long-lived npm token.
|
|
4
|
+
|
|
5
|
+
## One-Time npm Setup
|
|
6
|
+
|
|
7
|
+
Open the package settings on npm:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
https://www.npmjs.com/package/memento-mori-jester/access
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
Find the trusted publishing settings and add:
|
|
14
|
+
|
|
15
|
+
- Provider: `GitHub Actions`
|
|
16
|
+
- Organization or user: `Martin123132`
|
|
17
|
+
- Repository: `Memento-Mori`
|
|
18
|
+
- Workflow filename: `npm-publish.yml`
|
|
19
|
+
|
|
20
|
+
The workflow file must exist in `.github/workflows/`, which this repo now has.
|
|
21
|
+
|
|
22
|
+
## Manual Publish From GitHub
|
|
23
|
+
|
|
24
|
+
After the npm trusted publisher is configured:
|
|
25
|
+
|
|
26
|
+
1. Open the GitHub repo.
|
|
27
|
+
2. Go to `Actions`.
|
|
28
|
+
3. Open `npm Publish`.
|
|
29
|
+
4. Click `Run workflow`.
|
|
30
|
+
|
|
31
|
+
The workflow installs dependencies, runs tests, and publishes the current package version to npm.
|
|
32
|
+
|
|
33
|
+
## Why It Exists
|
|
34
|
+
|
|
35
|
+
Manual `npm publish` works, but npm asks for browser authentication. Trusted publishing moves that trust to the GitHub workflow and avoids storing a reusable npm token.
|
|
36
|
+
|
|
37
|
+
## Important
|
|
38
|
+
|
|
39
|
+
Only run the workflow after `package.json` has a version that npm does not already have. npm will reject publishing the same version twice.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "memento-mori-jester",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.5",
|
|
4
4
|
"description": "A local court-jester sidecar for AI coding agents: review plans, commands, diffs, and final claims before they get too pleased with themselves.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"repository": {
|