Repository navigation
Release 0.1.7: fulfillGate completes AI service orders - #6
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D3HHsGxGtwZRjZkvtgFC3P
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.
Requested by chris · project thread
Why
@proofable/sdk@0.1.6on npm sends noserviceParametersfromfulfillGate(), so an AI service order with a required input fails withSERVICE_PARAMETER_REQUIRED. The fix (7d437db) is onmainbut unreleased, while docs.proofable.me/sdks/gates already documents the working call. The launch path sells per-run AI services, so sellers on npm need it.What
package.jsonandpackage-lock.json: 0.1.6 to 0.1.7.CHANGELOG.md: the Unreleased fix becomes[0.1.7] - 2026-10-20, with compare links.Checks
npm run lint: 0 errors.npm test: 16 files, 212 tests pass.Release
Merging does not publish. Pushing tag
v0.1.7runs the Release workflow (tag must equal the package version) and publishes to npm. That push is chris's call.Generated by Claude Code