@redsift/charts 12.5.8 → 12.5.9-muiv6

package/CONTRIBUTING.md

@@ -420,22 +420,18 @@ yarn build:products
 
 ### Stable release
 
-1. Make sure you're on the release branch (ex: `release/vX.Y.Z`) and a PR is opened on Github
-2. Login to NPM with an authorized account: `npm login`
-3. Make sure your packages are up to date: `yarn`
-4. Make sure the CI entirely passed on Github
-5. (Optional) Make sure the build doesn't crash locally: `yarn build:design-system`
-6. Publish the packages to NPM: `yarn release vX.Y.Z`
+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).
+
+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.
 
 ### Alpha release
 
-If you need to test your contribution in a product before releasing -and you're not using `yarn link`, you can create an alpha release using the following process:
+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.
 
-1. Create an alpha release branch (ex: `release/vX.Y.Z-alpha.N`) based on `release/vX.Y.Z`
-2. Push it to remote (`git push origin release/vX.Y.Z-alpha.N`)
-3. Login to NPM with an authorized account: `npm login`
-4. Make sure your packages are up to date: `yarn`
-5. (Optional) Make sure the build doesn't crash: `yarn build:design-system`
-6. Publish the packages to NPM: `yarn release --dist-tag alpha vX.Y.Z-alpha.N`
+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)
 
-After that if you need to make modification to your contribution, go back to `release/vX.Y.Z` and make the necessary modifications. Then remove the alpha release branch, and redo the process from step 1, incrementing `N` by 1.
+To iterate, push more commits to the muiv8 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.8",
+  "version": "12.5.9-muiv6",
   "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.8-0",
-    "@redsift/popovers": "^12.5.8-0",
+    "@redsift/design-system": "^12.5.9-0",
+    "@redsift/popovers": "^12.5.9-0",
     "react": ">=17",
     "react-dom": ">=17",
     "styled-components": "6.1.19"
   },
-  "gitHead": "e91832d4957650451448df157ea290db6873254d"
+  "gitHead": "303004628960f198ea091b3128d363521d5106d4"
 }