chore: release v2.1.6 - #6
Closed
kky42 wants to merge 1 commit into
Closed
Conversation
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
2.1.6inpackage.jsonandpackage-lock.json, packaging the fix from PR fix(prompts): consolidate routing guidance and correct runtime claims #5 (prompt consolidation, active-tool gating, corrected workflow claims, and deterministic contract/scenario tests).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
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 succeedsversion consistency check: package.json and package-lock.json both read 2.1.6diff 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.