Skip to content

chore(release): consume @deepgram/agents from npm, drop sibling checkout, force 0.1.0#8

Merged
lukeocodes merged 1 commit intomainfrom
chore/release-prep-react-0.1.0
Apr 30, 2026
Merged

chore(release): consume @deepgram/agents from npm, drop sibling checkout, force 0.1.0#8
lukeocodes merged 1 commit intomainfrom
chore/release-prep-react-0.1.0

Conversation

@lukeocodes
Copy link
Copy Markdown
Member

Summary

phase 2 of the soft-launch release sequence. now that @deepgram/agents@0.1.1 is on npm, @deepgram/react can install it from the registry instead of a sibling checkout.

four things in one PR:

  1. drops cross-repo sibling checkout from @deepgram/react CI and publish workflows. each repo installs cross-repo deps from npm now.

  2. switches the agent dep to npm: packages/react/package.json now has "@deepgram/agents": "^0.1.1" instead of file:../../../agent/packages/sdk. the publish workflow no longer needs the file-pointer swap step.

  3. forces the first release to 0.1.0 via release-please's release-as. release-please was going to 1.0.0 because bump-minor-pre-major does not apply to the first release. release-as should be removed once 0.1.0 is tagged (post-launch follow-up).

  4. absorbs five dependabot PRs:

    • #2 setup-node v4 -> v6
    • #3 actions/checkout v4 -> v6
    • #5 typescript 5.9.3 -> 6.0.2
    • #6 googleapis/release-please-action v4 -> 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)

    v6 actions move off the deprecated node20 runtime onto node24.

Why

the previous CI used actions/checkout@v4 with path: ../agent to side-load the agent repo, then built @deepgram/agent locally before installing react. actions/checkout rejects 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 (with directory: packages/react for monorepo awareness), homepage, and bugs to packages/react/package.json upfront. 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/agent reference (imports, types, mocks, vite aliases, tsconfig paths, README, .agents notes) is now @deepgram/agents to match the SDK's npm name.

Test plan

  • bun install clean (resolves @deepgram/agents@0.1.1 from npm)
  • bun run typecheck clean
  • bun run build clean (dist/index.cjs 6.42 kB, gzipped 2.00 kB)
  • bun run test 35/35 passing
  • CI green on this PR
  • release-please opens release react 0.1.0 PR after merge
  • merge that PR -> @deepgram/react@0.1.0 on npm

Related

…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant