Repository navigation
chore(release): prepare the 0.1.0 npm release - #6
Closed
rahulrajaram wants to merge 2 commits into
Closed
rahulrajaram wants to merge 2 commits into
rahulrajaram wants to merge 2 commits into
Conversation
- Version 0.1.0 in package.json and a single src/version.ts used by every MCP server and client identity (was hardcoded 1.0.0), with a test that keeps the two in sync. - Ship only dist/, bin/, README.md and LICENSE (npm pack previously included tests/, harness/, .githooks/ and local agent state). - Drop postinstall: it ran tsc against src/, which a registry install does not have. The build now runs in prepare (local, git installs, pack and publish); typescript and @types/* move to devDependencies. - prepublishOnly runs the test suite; engines.node is >=20 to match CI. - Add repository, homepage and bugs metadata; README documents npm install and the node-pty install-script approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the 2026-09-27 multi-perspective review (run gptqueue-20260927-glm53): - not_claim_owner (acknowledge, renew) and actor_owned_elsewhere errors no longer name the owning session. A session id is a bearer credential for its agent, so echoing it let any participant that saw a claim id take over the owner's session (security F2). - The HTTP transport keeps sessions in a Map. Looking up a client-supplied mcp-session-id such as `constructor` in a plain object hit an inherited property: a 500 instead of 404, and with the idle sweep enabled a thrown close() that crashed the process (correctness F3). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
The 0.1.0 package preparation and credential/HTTP hardening are included in merged PR #8 with the additional review fixes. Closing this stacked PR as superseded. No npm release has been published. |
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.
Summary
Prepares gptqueue for its first npm release, 0.1.0. Stacked on #5; GitHub retargets this PR to
masteronce #5 merges.0.1.0inpackage.jsonand onesrc/version.tsused by every MCP server and client identity (these were hardcoded1.0.0). A test keeps the two in sync.filesallowlist ships onlydist/,bin/,README.mdandLICENSE(256 files, 208 KB). Without it,npm packshipped 598 files, includingtests/,harness/,.githooks/and local agent state.postinstallused to runtscagainstsrc/, which the published package does not include. The build moves toprepare(local, git, pack and publish), andtypescriptand@types/*move todevDependencies.prepublishOnlyruns the test suite.engines.nodeis>=20to match CI. Addsrepository,homepageandbugs.npm install -g gptqueueand thenode-ptyinstall-script approval that newer npm versions require.Validation
npm run buildpasses. Fullnpm test: 869 passed, 0 failed, 87 skipped.gptqueue-server: it reportsserverInfo.version: "0.1.0", and the Lua scripts are present underdist/.Review fixes (from the 2026-09-27 multi-perspective code review)
not_claim_owner(acknowledge, renew) andactor_owned_elsewhereerrors no longer name the owning session. A session ID is a bearer credential, so these messages allowed one agent to take over another's session.Map. A client-suppliedmcp-session-idsuch asconstructorused to resolve to an inherited object property: a 500 instead of a 404, and with the idle sweep enabled, a process crash. Regression test added; against the old code it fails with 500.npm test: 870 passed, 0 failed.Not in this PR
Publishing itself (tag
v0.1.0, GitHub release,npm publish) is pending a decision on how to publish: manually from a machine with npm credentials, or a tag-triggered workflow using anNPM_TOKENsecret.🤖 Generated with Claude Code