Skip to content

chore: release v2.1.6 - #6

Closed
kky42 wants to merge 1 commit into
mainfrom
fm/pi-flow-release-2-1-6
Closed

chore: release v2.1.6#6
kky42 wants to merge 1 commit into
mainfrom
fm/pi-flow-release-2-1-6

Conversation

@kky42

@kky42 kky42 commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Intent

Release PiFlow version 2.1.6 after merged PR #5 using the repository's established manual release path, without inventing release automation. Prepare the minimal version bump and accurate GitHub release notes covering profile-agnostic prompt consolidation, active-tool gating, corrected workflow claims, deterministic contract/scenario tests, and the opt-in bounded real-model routing E2E without claiming deterministic model behavior or cost improvements. Validate package contents, type checking, all tests, Node 22.x and 24.x support, version consistency, and dry-run packaging. Push only through a no-mistakes release PR and never merge it; stop at green checks for captain authorization. Publishing, then an annotated tag and GitHub Release, may occur only after explicit authorization for that exact merged release PR and re-verification of default branch and npm registry state; never weaken npm authentication, OTP, provenance, or other credential protections.

What Changed

Risk Assessment

✅ Low: The change is a three-location mechanical version bump with no logic, dependency, or configuration changes, fully consistent with the stated release process.

Testing

TypeScript compilation, the full local test suite (179 tests), and a dry-run pack all pass for @kky42/pi-flow@2.1.6. The release commit is exactly the minimal version bump the intent requires, with no other source changes.

Evidence: check + dry-run pack output
> @kky42/pi-flow@2.1.6 check
> tsc --noEmit && vitest run

 RUN  v3.2.4

 ✓ test/agent-rendering.test.ts (4 tests) 31ms
 ✓ test/pi-backend-behavior.test.ts (10 tests) 136ms
 ✓ test/agent-concurrency.test.ts (7 tests) 181ms
 ✓ test/agent-progress.test.ts (10 tests) 282ms
 ✓ test/e2e-basic-metrics.test.ts (8 tests) 5ms
 ✓ test/agent-contract.test.ts (8 tests) 509ms
 ✓ test/concurrency.test.ts (8 tests) 6ms
 ✓ test/stream.test.ts (5 tests) 2ms
 ✓ test/workflow.test.ts (63 tests) 900ms
 ✓ test/timeout.test.ts (1 test) 1ms
 ✓ test/profiles.test.ts (5 tests) 22ms
 ✓ test/headless.test.ts (11 tests) 135ms
 ✓ test/delegation-scenarios.test.ts (3 tests) 57ms
 ✓ test/workflow-integration.test.ts (13 tests) 1737ms
 ✓ test/e2e-deepseek-claude-env.test.ts (6 tests) 4105ms
 ✓ test/claude-backend.test.ts (6 tests) 6587ms
 ✓ test/codex-backend.test.ts (11 tests) 9797ms

 Test Files  17 passed (17)
      Tests  179 passed (179)
   Duration  12.28s

--- npm pack --dry-run ---
npm notice package: @kky42/pi-flow@2.1.6
npm notice version: 2.1.6
npm notice filename: kky42-pi-flow-2.1.6.tgz
npm notice package size: 315.9 kB
npm notice unpacked size: 747.5 kB
npm notice total files: 91
npm notice (prepack build: tsc -p tsconfig.dist.json + rewrite-dts-extensions, 17 .d.ts files rewritten)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

  • npm run check — tsc --noEmit + vitest run (179 tests, 17 files)
  • npm pack --dry-run — verified tarball is @kky42/pi-flow@2.1.6, 91 files, 315.9 kB, prepack dist build succeeds
  • version consistency check: package.json and package-lock.json both read 2.1.6
  • diff inspection: release commit touches only package.json and package-lock.json
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

@kky42

kky42 commented Aug 2, 2026

Copy link
Copy Markdown
Owner Author

Superseded by the v2.1.6 release from main at 00f73b3, which includes the version bump together with the prompt and workflow guidance improvements.

@kky42 kky42 closed this Aug 2, 2026
@kky42
kky42 deleted the fm/pi-flow-release-2-1-6 branch August 2, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant