@redsift/charts 12.5.10 → 12.5.11

package/CONTRIBUTING.md

@@ -48,7 +48,7 @@ The Design System is following a monorepo architecture, providing multiple packa
 
 - `@redsift/table`
 
-  This package provides datagrid components and features based on [MUI DataGrid](https://mui.com/x/react-data-grid/). The muiv6 and muiv7 branches use MUI DataGrid Pro; muiv8 (main) uses MUI DataGrid Premium. A [Pro or Premium license](https://mui.com/x/introduction/licensing/) from MUI is required.
+  This package provides datagrid components and features based on [MUI DataGrid](https://mui.com/x/react-data-grid/). The muiv6 branch uses MUI DataGrid Pro; the default line (`main`) uses MUI DataGrid Premium. A [Pro or Premium license](https://mui.com/x/introduction/licensing/) from MUI is required.
 
 - `@redsift/charts`
 
@@ -416,22 +416,22 @@ yarn build:products
 
 ## Publishing a release
 
-> **Canonical process:** the full, up-to-date release workflow — the three parallel MUI DataGrid version lines (muiv6 / muiv7 / muiv8), peer-dependency bumps, docs/MCP regeneration and the pre-release checklist — lives in **`.github/instructions/release.instructions.md`**. Follow that as the source of truth. The steps below are a simplified single-line summary and omit the multi-version release details.
+> **Canonical process:** the full, up-to-date release workflow — the two parallel MUI DataGrid version lines (default / muiv6), peer-dependency bumps, docs/MCP regeneration and the pre-release checklist — lives in **`.github/instructions/release.instructions.md`**. Follow that as the source of truth. The steps below are a simplified single-line summary and omit the multi-version release details.
 
 ### Stable release
 
-Releases go through the one-command `yarn release` CLI — not a manual `lerna publish`. See `.github/instructions/release.instructions.md` for the full flow (all three lines, pre-release checklist, post steps).
+Releases go through the one-command `yarn release` CLI — not a manual `lerna publish`. See `.github/instructions/release.instructions.md` for the full flow (both lines, pre-release checklist, post steps).
 
 1. Login to NPM with an authorized account: `npm login`
-2. Dry-run the readiness gate on all three lines: `yarn release stable X.Y.Z --dry-run` (validates each line and stops before anything irreversible)
-3. When green, publish: `yarn release stable X.Y.Z` — the CLI preflights, then publishes `X.Y.Z-muiv6`, `X.Y.Z-muiv7`, and `X.Y.Z`, pausing only for the per-line npm OTP. It then creates the GitHub release notes, opens (never merges) the `release/X.Y.Z-muiv8` → `main` PR, and cuts the next release branches.
+2. Dry-run the readiness gate on both lines: `yarn release stable X.Y.Z --dry-run` (validates each line and stops before anything irreversible)
+3. When green, publish: `yarn release stable X.Y.Z` — the CLI preflights, then publishes `X.Y.Z-muiv6` and `X.Y.Z`, pausing only for the per-line npm OTP. It then creates the GitHub release notes, opens (never merges) the `release/X.Y.Z` → `main` PR, and cuts the next release branches.
 
 ### Alpha release
 
-If you need to test your contribution in a product before releasing — and you're not using `yarn link` — publish to the live alpha channel (muiv8-based, npm dist-tag `alpha`). There are no per-feature alpha branches to create or recreate.
+If you need to test your contribution in a product before releasing — and you're not using `yarn link` — publish to the live alpha channel (default-line-based, npm dist-tag `alpha`). There are no per-feature alpha branches to create or recreate.
 
 1. Login to NPM with an authorized account: `npm login`
-2. Check out the current muiv8 release branch: `git checkout release/X.Y.Z-muiv8`
-3. Publish: `yarn release alpha` — the CLI derives the next `X.Y.Z-muiv8-alpha.N` from the tags, runs the single-line preflight, and publishes (only the npm OTP is manual)
+2. Check out the current default release branch: `git checkout release/X.Y.Z`
+3. Publish: `yarn release alpha` — the CLI derives the next `X.Y.Z-alpha.N` from the tags, runs the single-line preflight, and publishes (only the npm OTP is manual)
 
-To iterate, push more commits to the muiv8 branch and run `yarn release alpha` again.
+To iterate, push more commits to the default release branch and run `yarn release alpha` again.

package/package.json

@@ -30,7 +30,7 @@
     "test": "yarn test:unit && yarn test:storybook"
   },
   "types": "index.d.ts",
-  "version": "12.5.10",
+  "version": "12.5.11",
   "dependencies": {
     "@emotion/react": "^11.10.4",
     "@emotion/styled": "^11.10.4",
@@ -86,11 +86,11 @@
     "ts-jest": "^29.2.0"
   },
   "peerDependencies": {
-    "@redsift/design-system": "^12.5.10-0",
-    "@redsift/popovers": "^12.5.10-0",
+    "@redsift/design-system": "^12.5.11-0",
+    "@redsift/popovers": "^12.5.11-0",
     "react": ">=17",
     "react-dom": ">=17",
     "styled-components": "6.1.19"
   },
-  "gitHead": "cbca2da017f0a67840735412477a9c2b9354d413"
+  "gitHead": "c652970363e8113ea507d6258c554d5477a74a0e"
 }