task-pipeline-skill 1.7.0 → 1.7.1
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
CHANGED
|
@@ -1,5 +1,33 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## v1.7.1 — 2026-08-03
|
|
4
|
+
|
|
5
|
+
### Fixed — the tag-ancestry gate had been failing on every release since v1.6.1
|
|
6
|
+
|
|
7
|
+
The step that exists so *"a release does not live only on a tag"* — added after the
|
|
8
|
+
v1.4.4 incident — **failed on every tag from v1.6.1 onward**, and nobody saw it,
|
|
9
|
+
because `release` ran green beside it and the failing log showed only the echoed
|
|
10
|
+
script with no output of its own.
|
|
11
|
+
|
|
12
|
+
`git fetch --tags` without `--force` aborts with *"would clobber existing tag"* when
|
|
13
|
+
the checkout has already created `refs/tags/<tag>` locally and the tag is
|
|
14
|
+
**annotated**. `set -eu` then killed the step before its first `echo` — which is why
|
|
15
|
+
the log was blank and read as though the ancestry check itself had found something.
|
|
16
|
+
v1.6.1 was the first tag cut with `git tag -a`; every one since inherited it.
|
|
17
|
+
|
|
18
|
+
Two changes, and the second matters more than the first:
|
|
19
|
+
|
|
20
|
+
- `--force` on the tag fetch, with a printed note if it still degrades.
|
|
21
|
+
- **The step now says which failure it is.** If `refs/remotes/origin/main` cannot be
|
|
22
|
+
resolved, every tag looks like an orphan and the old wording reported a
|
|
23
|
+
catastrophe that was really a missing ref. It now fails with that sentence
|
|
24
|
+
instead, and on success prints the tag count and the `main` it checked against.
|
|
25
|
+
|
|
26
|
+
This is the shape the repo's own doctrine names: a gate whose exit code nobody reads
|
|
27
|
+
is a gate that has stopped guarding — `references/gates.md` → *A gate's exit code is
|
|
28
|
+
part of its output*, and `references/learned.md` rule 11. It was found by watching
|
|
29
|
+
the release this release shipped, which is the only reason it was found at all.
|
|
30
|
+
|
|
3
31
|
## v1.7.0 — 2026-08-03
|
|
4
32
|
|
|
5
33
|
### Added — documentation is a deliverable, and it has a gate
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "task-pipeline-skill",
|
|
3
|
-
"version": "1.7.
|
|
3
|
+
"version": "1.7.1",
|
|
4
4
|
"description": "Full-cycle delivery pipeline for coding agents: a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine ships inside the skill — no companion plugin required. This package is the installer CLI.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"task-pipeline": "bin/task-pipeline.js"
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "task-pipeline",
|
|
3
3
|
"displayName": "Task Pipeline",
|
|
4
4
|
"description": "Runs a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/manual gates, a frozen requirement spine that must close with evidence, a loop guard that breaks churn, one provider-agnostic model confirmed up front, and an optional super-ux UX track for user-facing work.",
|
|
5
|
-
"version": "1.7.
|
|
5
|
+
"version": "1.7.1",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "ssheleg",
|
|
8
8
|
"url": "https://x.com/sshlg93"
|