@hanna84/mcp-writing 1.4.7 → 1.4.8
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/CHANGELOG.md +10 -0
- package/README.md +1 -35
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,11 +4,21 @@ All notable changes to this project will be documented in this file. Dates are d
|
|
|
4
4
|
|
|
5
5
|
Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
|
|
6
6
|
|
|
7
|
+
#### [v1.4.8](https://github.com/hannasdev/mcp-writing.git
|
|
8
|
+
/compare/v1.4.7...v1.4.8)
|
|
9
|
+
|
|
10
|
+
- docs: move release automation out of README [`#41`](https://github.com/hannasdev/mcp-writing.git
|
|
11
|
+
/pull/41)
|
|
12
|
+
|
|
7
13
|
#### [v1.4.7](https://github.com/hannasdev/mcp-writing.git
|
|
8
14
|
/compare/v1.4.6...v1.4.7)
|
|
9
15
|
|
|
16
|
+
> 19 April 2026
|
|
17
|
+
|
|
10
18
|
- docs: remove publish workflow badge to avoid status confusion [`#40`](https://github.com/hannasdev/mcp-writing.git
|
|
11
19
|
/pull/40)
|
|
20
|
+
- Release 1.4.7 [`a0b1dd3`](https://github.com/hannasdev/mcp-writing.git
|
|
21
|
+
/commit/a0b1dd39bdb7e7a25d4892ee5d2a4227a6618900)
|
|
12
22
|
|
|
13
23
|
#### [v1.4.6](https://github.com/hannasdev/mcp-writing.git
|
|
14
24
|
/compare/v1.4.5...v1.4.6)
|
package/README.md
CHANGED
|
@@ -447,41 +447,7 @@ Unit tests use an in-memory SQLite database and temporary directories — no ser
|
|
|
447
447
|
|
|
448
448
|
For real projects, keep your manuscript sync folder outside this tool repository and point `WRITING_SYNC_DIR` at that external path.
|
|
449
449
|
|
|
450
|
-
Maintainers: see `AGENT.md` for persistent
|
|
451
|
-
|
|
452
|
-
## Release automation
|
|
453
|
-
|
|
454
|
-
This repository uses a `release-it` workflow (modeled after `n8n-nodes-bambulab`) instead of Release Please.
|
|
455
|
-
|
|
456
|
-
How it works:
|
|
457
|
-
|
|
458
|
-
1. A PR is merged into `main`.
|
|
459
|
-
2. `.github/workflows/release.yml` runs on that push.
|
|
460
|
-
3. The workflow fetches tags and infers version bump type from commits since last tag:
|
|
461
|
-
- `BREAKING CHANGE` or `!:` -> major
|
|
462
|
-
- `feat:` -> minor
|
|
463
|
-
- everything else -> patch
|
|
464
|
-
4. `release-it` creates a `Release x.y.z` commit and `vx.y.z` tag.
|
|
465
|
-
5. Tag push triggers `.github/workflows/publish.yml` to publish to npm.
|
|
466
|
-
|
|
467
|
-
Required setup:
|
|
468
|
-
|
|
469
|
-
- Repository secret: `RELEASE_DEPLOY_KEY` (private SSH key for a repo deploy key with write access)
|
|
470
|
-
- Optional secret: `RELEASE_DEPLOY_KNOWN_HOSTS` (additional strict host keys; GitHub host key is already handled)
|
|
471
|
-
- Branch rules must allow the **Deploy Key** actor to bypass PR-only rule for release commit/tag push
|
|
472
|
-
- Repository URL in `package.json` must remain valid for npm provenance
|
|
473
|
-
|
|
474
|
-
Local dry-run (optional):
|
|
475
|
-
|
|
476
|
-
```sh
|
|
477
|
-
npm run release -- --ci --dry-run
|
|
478
|
-
```
|
|
479
|
-
|
|
480
|
-
Operational note:
|
|
481
|
-
|
|
482
|
-
- If a release job partially succeeds by pushing a tag before failing later, do not rerun that old workflow run.
|
|
483
|
-
- The workflow now fails fast when `package.json` is behind the latest tag, which indicates a stale rerun.
|
|
484
|
-
- In that case, trigger the next release from current `main` instead of retrying the old run.
|
|
450
|
+
Maintainers: see `MAINTAINERS.md` for release and operational setup notes, and `AGENT.md` for persistent workflow conventions and release/recovery guidance.
|
|
485
451
|
|
|
486
452
|
## Troubleshooting
|
|
487
453
|
|