Release kimetsu-pi 0.1.4 with refreshed docs and dependencies - #9
Merged
Merged
Conversation
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
1 participant
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.
Release kimetsu-pi 0.1.4 with the memory freshness, longer session-save deadline, and improved reuse/correction guidance merged in #5.
Refresh the README with tested Pi/Kimetsu versions, project setup, pinned and latest-version upgrades, and the distinction between local retrieval and configured model-based saving. Link benchmark claims to the core project's evaluation notes. Bump package and lockfile versions together.
Dependency PRs #6, #7, and #8 are merged: Pi 0.85.1, Vitest 5.0.0, updated Node types, checkout 7.0.1, and setup-node 7.0.0. The earlier Vitest security PR #4 is superseded and closed; npm audit reports zero vulnerabilities.
Validation: 34 tests pass with the real Kimetsu 2.8.0 CLI on Node 22.19.0; typecheck, audit, and package dry-run pass. All dependency PRs passed mandatory three-platform CI. The release tag will be created only after this PR merges and its exact main commit passes CI, then the existing workflow will publish with provenance.