Repository navigation
build: target pi 1.2.0, and pin the install to v0.1.0 - #6
Merged
Merged
Conversation
The plugin builds and tests against Pi 1.2.0, and the readme installs that Pi. peerDependencies accept 0.99.1 up to Pi 2 in place of any version. The readme installs the v0.1.0 tag rather than main. The package drops publishConfig: it is installed from git, not npm. The changelog dates 0.1.0 today.
Coverage |
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.
Purpose
The last changes before tagging 0.1.0.
pi-ai,pi-coding-agent,pi-tui,pi-durablefrom 1.0.3), and thechorddependency too. The README installs Pi 1.2.0, and its badge says so.peerDependencies:>=0.99.1 <2instead of*, so a future Pi 2 gets a warning.pi install git:github.com/leverage-computer/pi-plugin@v0.1.0instead of whatever is onmain. The tag doesn't exist yet, so tag right after merging.publishConfigremoved: the plugin installs from git, not npm.filesand the CI pack check stay, which keeps publishing to npm possible later.Verification
All with Bun 1.4.2 from the Nix shell:
bun install --frozen-lockfile, thenbun run checkpasses: Biome, ESLint,tsc, 78 of 78 tests, and the build.bun pm pack --dry-runlists 20 files.pi-durable1.0.3) with the newchord1.2.0 backs the lower bound.tscpasses. The suite passed 78 of 78 once and 77 of 78 once.