chore(release): unpin release-as 0.1.0 so release-please bumps properly#30
Merged
lukeocodes merged 1 commit intomainfrom May 6, 2026
Merged
Conversation
…g entry The release-please config still had `release-as: 0.1.0` from the original release pin (commit 53a4f04). That kept release-please from ever bumping past 0.1.0: - PR #29 (autogenerated release for the fix(ui) commit) was titled "release ui 0.1.0" and added a duplicate `## [0.1.0]` changelog entry that compared 0.1.0 to itself. - On merge, release-please tried to re-create tag `ui-v0.1.0`, which already existed from the original 2026-04-30 release. GitHub responded with "already_exists" and the workflow failed. - Net effect: my CSS scoping fix (commit 8742c18) is in main but not on npm. npm still has the original unfixed 0.1.0. Fix: - Remove `release-as: 0.1.0` so release-please bumps from conventional commits going forward. - Delete the duplicate `## [0.1.0]` block PR #29 added to the changelog. The next release-please PR will re-add it under the correct bumped version (0.1.1 per `bump-patch-for-minor-pre-major: true` plus the existing `fix:` commit). After this lands release-please will open a new PR titled 'release ui 0.1.1' (or 0.2.0 depending on what other commits are in the queue). Merging that will publish the fix to npm and trigger the CDN deploy.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
lukeocodes
added a commit
to deepgram/agent
that referenced
this pull request
May 6, 2026
#48) ## Why `@deepgram/ui@0.1.1` (just published from [deepgram/ui#27](deepgram/ui#27) + [deepgram/ui#30](deepgram/ui#30)) ships preflight scoped to `[data-dg-agent]` via [`tailwindcss-scoped-preflight`](https://github.com/Roman86/tailwindcss-scoped-preflight). Until the widget bumps its dependency, the published UMD on `cdn.deepgram.com/widgets/` still ships unscoped Tailwind preflight that bleeds into host pages. Symptoms reported in [deepgram/deepgram-docs#777](deepgram/deepgram-docs#777): content width collapsed on every non-demo page on the docs site after the widget bundle finished loading. Same regression hits any customer embedding the widget on their own site. ## What changed - `packages/widget/package.json`: `@deepgram/ui` `^0.1.0` → `^0.1.1` - `bun.lock` regenerated ## Verification Rebuilt the widget locally against `@deepgram/ui@0.1.1`: | | before | after | |---|---|---| | Unscoped `@layer base{*,:after,…}` rules in widget UMD | many | **0** | | `:where([data-dg-agent], …)` scoped rules | 0 | **76** | | Total `[data-dg-agent]` occurrences | 9 | **171** | Bundle size: 384.30 KB → 387.53 KB (+3.23 KB) from the added scope selectors. Acceptable trade. ## Expected after merge 1. release-please opens `chore(main): release agents-widget 0.1.4`. 2. Merging that PR bumps `packages/widget/package.json` to 0.1.4 and tags `agents-widget-v0.1.4`. 3. The npm publish workflow pushes `@deepgram/agents-widget@0.1.4` to npm. 4. The CDN publish job uploads the new UMD bundle to: - `https://cdn.deepgram.com/widgets/v0.1.4/widget.umd.js` (immutable, 365-day TTL) - `https://cdn.deepgram.com/widgets/latest/widget.umd.js` (5-min TTL plus invalidation) 5. Anyone loading either URL gets the scoped preflight. ## Refs - [deepgram/ui#27](deepgram/ui#27) — the source fix - [deepgram/ui#30](deepgram/ui#30) — unpin release-please to actually publish 0.1.1 - [deepgram/dx-stack#4](deepgram/dx-stack#4) — recipe + gotchas doc - [deepgram/deepgram-docs#777](deepgram/deepgram-docs#777) — where the bleed was first surfaced
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.
Why
npm Publish run 25445857328 failed with
Validation Failed: Release tag_name already_exists.Trace:
release-please-config.jsonstill hadrelease-as: "0.1.0"from commit 53a4f04 ("force 0.1.0" for the original release).release ui 0.1.0(the pinned version), with a duplicate## [0.1.0]changelog entry that compares 0.1.0 to itself.ui-v0.1.0. That tag already existed from the 2026-04-30 release.@deepgram/ui@0.1.0on npm is still the OLD pre-fix bundle.Fix
release-as: "0.1.0"so release-please bumps from conventional commits.## [0.1.0]block PR chore(main): release ui 0.1.0 #29 wrote into the changelog. The next release-please PR will re-add the entry under the correct bumped version.Expected after merge
release-please opens a new PR titled something like
chore(main): release ui 0.1.1(withbump-patch-for-minor-pre-major: true+ the existingfix:commit).Merging that PR will:
packages/ui/package.jsonto 0.1.1ui-v0.1.1@deepgram/ui@0.1.1to npm with the scoped-preflight fix@deepgram/uiitself; the fix only reaches the agents-widget CDN once@deepgram/agents-widgetbumps its dependency on@deepgram/uiand re-publishes its UMD bundle.)Follow-up
Once
@deepgram/ui@0.1.1is on npm, bump@deepgram/agents-widget's@deepgram/uidependency to^0.1.1so the next widget release picks up the fix end-to-end.