chore(release): consume @deepgram/agents from npm, drop sibling checkout, force 0.1.0#8
Merged
lukeocodes merged 1 commit intomainfrom Apr 30, 2026
Merged
Conversation
…out, force 0.1.0 update @deepgram/react to consume @deepgram/agents from npm at ^0.1.1 instead of via file: pointer to a sibling checkout. drops the sibling-repo checkout from CI and the publish workflow, simplifies publish (no more file-pointer swap), bumps action versions, and forces the first release to 0.1.0 via release-please's release-as. absorbs dependabot #2 (setup-node v6), #3 (checkout v6), #5 (typescript 6.0.2), #6 (release-please-action v5), #7 (deps group: happy-dom 20.9.0, react 19.2.5, react-dom 19.2.5, terser 5.46.2, vite 8.0.10). adds repository/homepage/bugs to packages/react/package.json upfront so npm provenance does not reject the publish (lesson learned from the @deepgram/agents 0.1.0 -> 0.1.1 hotfix). verified locally: typecheck clean, build clean (6.42 kB cjs), 35/35 tests passing.
This was referenced Apr 30, 2026
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
phase 2 of the soft-launch release sequence. now that
@deepgram/agents@0.1.1is on npm,@deepgram/reactcan install it from the registry instead of a sibling checkout.four things in one PR:
drops cross-repo sibling checkout from
@deepgram/reactCI and publish workflows. each repo installs cross-repo deps from npm now.switches the agent dep to npm:
packages/react/package.jsonnow has"@deepgram/agents": "^0.1.1"instead offile:../../../agent/packages/sdk. the publish workflow no longer needs the file-pointer swap step.forces the first release to 0.1.0 via release-please's
release-as. release-please was going to 1.0.0 becausebump-minor-pre-majordoes not apply to the first release.release-asshould be removed once 0.1.0 is tagged (post-launch follow-up).absorbs five dependabot PRs:
#2setup-node v4 -> v6#3actions/checkout v4 -> v6#5typescript 5.9.3 -> 6.0.2#6googleapis/release-please-action v4 -> v5#7deps group (happy-dom 20.9.0, react 19.2.5, react-dom 19.2.5, terser 5.46.2, vite 8.0.10)v6 actions move off the deprecated node20 runtime onto node24.
Why
the previous CI used
actions/checkout@v4withpath: ../agentto side-load the agent repo, then built@deepgram/agentlocally before installing react.actions/checkoutrejects paths outside$GITHUB_WORKSPACE, so this had been failing on every CI run. treating cross-repo deps as plain npm deps removes the whole class of problem.Repository metadata
added
repository(withdirectory: packages/reactfor monorepo awareness),homepage, andbugstopackages/react/package.jsonupfront. the agent SDK had to ship a 0.1.0 -> 0.1.1 hotfix because npm provenance rejected publish without these fields. doing it now avoids the same dance for react.Renames
every
@deepgram/agentreference (imports, types, mocks, vite aliases, tsconfig paths, README, .agents notes) is now@deepgram/agentsto match the SDK's npm name.Test plan
bun installclean (resolves@deepgram/agents@0.1.1from npm)bun run typecheckcleanbun run buildclean (dist/index.cjs6.42 kB, gzipped 2.00 kB)bun run test35/35 passingrelease react 0.1.0PR after merge@deepgram/react@0.1.0on npmRelated
@deepgram/agents@0.1.1already being on npm (verified)deepgram/ui), then phase 4 (@deepgram/agents-widgetback in deepgram/agent)