Release datapipe-client 0.1.0 - #242
Merged
Merged
Conversation
Published to npm by hand, because a trusted publisher cannot be attached to a package that does not exist yet -- `npm trust github` answers 404 on POST /-/package/datapipe-client/trust until the name is claimed. That was an open question in the runbook; it is now settled, and the automation takes over from here. This is what `changeset version` produced: the bump from the placeholder 0.0.0, the changelog, and the initial changeset consumed. Committing it keeps the repository agreeing with the registry, so the next release computes 0.1.1 rather than trying to republish. Verified against the registry rather than assumed: `npm install datapipe-client` in a clean directory resolves, all eight exports are present, getBaseURL() returns the production default, and unpkg.com/datapipe-client serves the browser bundle that defines the DataPipe global -- the URL the docs already tell researchers to use. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SgDfss2zhjwMky2mBKbcBX
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.
datapipe-client@0.1.0is on npm: https://www.npmjs.com/package/datapipe-clientThis commits what
changeset versionproduced — the bump from the placeholder0.0.0, the changelog, and the initial changeset consumed — so the repository agrees with the registry and the next release computes0.1.1rather than trying to republish.Why it was published by hand
A trusted publisher cannot be attached to a package that does not exist.
npm trust github datapipe-client ...answers:The runbook hedged on this ("may need the package to exist"); it is now settled. Publish first, then register the trust, then the automation takes over. #241 updates the runbook to say so, along with two other things this exercise turned up.
Verified against the registry, not assumed
npm install datapipe-clientin a clean directory resolves and loads.createSession,startSession,saveData,saveBase64Data,getCondition,setBaseURL,getBaseURL,DataPipeSession.getBaseURL()returnshttps://pipe.jspsych.org.https://unpkg.com/datapipe-clientreturns 200 and serves a bundle defining theDataPipeglobal — the exact URL the docs already tell plain-JavaScript researchers to use, which was 404ing until now.What this unblocks
The plain-JavaScript "Save as you go" tab on the test site now works rather than pointing at a missing package. Next: regenerate the jsPsych lockfile so jspsych/jsPsych#3718 can leave draft, then PR #188.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SgDfss2zhjwMky2mBKbcBX