@sanity/ui 3.5.1 → 3.5.3

package/README.md

@@ -9,7 +9,7 @@ npm install @sanity/ui
 npm install react react-dom styled-components
 ```
 
-[![npm version](https://img.shields.io/npm/v/@sanity/ui.svg?style=flat-square)](https://www.npmjs.com/package/@sanity/ui)
+[![npm version](https://img.shields.io/npm/v/%40sanity%2Fui/release-v3?style=flat-square)](https://www.npmjs.com/package/@sanity/ui/v/release-v3)
 
 ## Usage
 
@@ -38,7 +38,7 @@ When you make a change that should be released, add a changeset to your pull req
 pnpm changeset
 ```
 
-Once pull requests with changesets are merged into the `main` branch, a "Version Packages" pull request is opened (and kept up to date) that bumps the affected package versions and updates their changelogs. Merging that pull request publishes the packages to npm through the [`Release` workflow](https://github.com/sanity-io/ui/actions/workflows/release.yml), which uses npm [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) (OIDC).
+Once pull requests with changesets are merged into the `v3` branch, a "Version Packages" pull request is opened (and kept up to date) that bumps the affected package versions and updates their changelogs. Merging that pull request publishes the packages to npm under the `release-v3` dist-tag through the [`Release` workflow](https://github.com/sanity-io/ui/actions/workflows/release.yml), which uses npm [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) (OIDC). The `latest` dist-tag tracks releases from `main`.
 
 ## License
 

package/dist/_chunks/getScopedTheme.cjs

@@ -1285,7 +1285,7 @@ function merge(...records) {
 function _merge(acc, source) {
 	for (let key of Object.keys(source)) {
 		let prevValue = acc[key], nextValue = source[key];
-		isRecord(prevValue) && isRecord(nextValue) ? acc[key] = merge(prevValue, nextValue) : acc[key] = nextValue;
+		acc[key] = isRecord(prevValue) && isRecord(nextValue) ? merge(prevValue, nextValue) : nextValue;
 	}
 	return acc;
 }