chore(main): release agents-widget 0.1.0#32
Closed
github-actions[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
Merged
7 tasks
Member
|
closing — this branch was generated before PR #31 (rename to @deepgram/agents) and PR #34/#35 (SDK 0.1.1 release). its manifest conflict on |
lukeocodes
added a commit
that referenced
this pull request
Apr 30, 2026
…t/ui from npm, force 0.1.0 (#36) ## Summary phase 4 (final) of the soft-launch sequence. with `@deepgram/agents@0.1.1`, `@deepgram/react@0.1.0`, and `@deepgram/ui@0.1.0` on npm, `@deepgram/agents-widget` can install everything from the registry and ship as a self-contained CDN-style UMD bundle. ## Release plan recap 1. `@deepgram/agents` -> npm ✅ (0.1.1) 2. `@deepgram/react` -> npm ✅ (0.1.0) 3. `@deepgram/ui` -> npm ✅ (0.1.0) 4. **`@deepgram/agents-widget`** -> npm ← this PR ## Changes ### Workspaces - `package.json` (root): widget + examples back in the `workspaces` array (they were temporarily pulled in phase 1 so the SDK could publish first). scripts widen to filter both `@deepgram/agents` and `@deepgram/agents-widget`. ### Widget package - `packages/widget/package.json`: `@deepgram/react` and `@deepgram/ui` switched from `file:` pointers to `^0.1.0` npm versions. `@deepgram/agents` stays at `workspace:*` (same monorepo). `repository` (with `directory: packages/widget`), `homepage`, and `bugs` added upfront — npm provenance won't reject the publish. - `packages/widget/vite.config.ts`: drops the file-system path aliases for `@deepgram/agents`/`@deepgram/react`/`@deepgram/ui`. node_modules resolution handles them normally now. preact aliases kept (those are string-id redirects, not deepgram packages). - `packages/widget/tsconfig.json`: drops the deepgram path mappings and the cross-repo project references. preact paths kept. ### Examples - `examples/package.json`: `@deepgram/react` and `@deepgram/ui` switched to `^0.1.0` from npm. `@deepgram/agents` and `@deepgram/agents-widget` stay at `workspace:*`. ### Workflows - `.github/workflows/npm-publish.yml`: `publish-widget` no longer checks out sibling repos or builds them. Just `bun install` + `bun run build` + `npm publish`. the file-pointer-swap step shrank to a single-line pin of `@deepgram/agents` to whatever SDK version is being released in the same workflow run. - `.github/workflows/ci.yml`: `actions/setup-node@v6` added before bun (avoids astro-style runtime mismatches that bit phase 3). ## What this does NOT include - `publish.yml` (CDN upload of widget UMD to `cdn.deepgram.com/widgets/`) is unchanged. it triggers on `release: published` which doesn't fire for releases created by GITHUB_TOKEN-backed release-please-action (same guard that bit ui phase 3). there's also no widget CDN bucket yet, so this is moot for now. revisit when the bucket exists, at which point the `cdn-sync` job pattern from ui can be applied here too. ## Test plan - [x] `bun install` clean (resolves `@deepgram/react@0.1.0` and `@deepgram/ui@0.1.0` from npm) - [x] `bun run typecheck` clean for SDK and widget - [x] `bun run test` 107/107 passing (78 SDK + 29 widget) - [x] `bun run build` clean. SDK `dist/index.js` 11.06 kB / 3.67 kB gzipped. widget `dist/widget.es.js` 388.58 kB / 90.02 kB gzipped, `dist/widget.umd.js` 384.30 kB / 90.06 kB gzipped. - [ ] CI green on this PR - [ ] release-please-please #32 regenerates as `release agents-widget 0.1.0` after merge - [ ] merge that PR -> `@deepgram/agents-widget@0.1.0` on npm ## Related - depends on `@deepgram/react@0.1.0` and `@deepgram/ui@0.1.0` on npm (verified) - regenerates #32 (release-please widget PR currently at 0.1.0 from before the rename) - closes the soft-launch sequence
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.
🤖 I have created a release beep boop
0.1.0 (2026-04-30)
Features
Bug Fixes
Refactors
This PR was generated with Release Please. See documentation.