@redsift/table 12.5.6 → 12.5.7-muiv6

package/CONTRIBUTING.md

@@ -101,6 +101,10 @@ import { sum as d3sum, scaleOrdinal as d3scaleOrdinal, ScaleOrdinal as d3ScaleOr
 
 ## Component
 
+### Design principles
+
+Before any design/API decision (defaults, adding/exposing styling or spacing props), follow [`docs/design-guidelines.md`](docs/design-guidelines.md) and reference principles by slug (e.g. `DS-SPACING-01`) in code, PRs and reviews.
+
 ### Scaffolding
 
 Each component should be in its own folder. If a subcomponent can be used as a standalone component, it should be in its own folder too. For instance, `CheckboxGroup` uses `Checkbox` but `Checkbox` can be used alone. In this case, `CheckboxGroup` and `Checkbox` both have their own folder. For `PieChart` and `PieChartSlice`, a `PieChartSlice` can not be used alone. It only exists inside a `PieChart` component. Therefore, both components are inside the same folder.
@@ -412,6 +416,8 @@ 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.
+
 ### Stable release
 
 1. Make sure you're on the release branch (ex: `release/vX.Y.Z`) and a PR is opened on Github

package/_internal/BaseComponents.js

@@ -1,3 +1,3 @@
-export { B as BaseButton, a as BaseCheckbox, b as BaseIcon, c as BaseIconButton, m as muiIconToDSIcon } from './BaseIconButton.js';
+export { B as BaseButton, a as BaseCheckbox, b as BaseIcon, c as BasePopper, m as muiIconToDSIcon } from './BasePopper.js';
 export { B as BaseTextField } from './BaseTextField.js';
 //# sourceMappingURL=BaseComponents.js.map