esender-email-editor 1.2.1 → 1.3.0

package/README.md

@@ -163,8 +163,6 @@ The editor does **not** mount its own `<ConfigProvider>` or antd `<App />`. It i
 
 All editor-specific CSS lives under a single `.aee-root` class scope (the wrapper div around the editor), so SCSS overrides and resets cannot reach host components either.
 
-If you want the editor branded purple like the default screenshots, wrap your host app in your own `<ConfigProvider theme={{ token: { colorPrimary: '#7747ff' } }}>` — the editor will inherit it.
-
 ## License handshake
 
 The editor will not render until the eSender license is verified:
@@ -287,36 +285,6 @@ import Package, {
 | `You cannot render a <Router> inside another <Router>` | You're on an outdated version. Update — current package uses `MemoryRouter` internally. |
 | Renders during SSR throw | Mount the component client-side only (see Next.js example above). |
 
-## Publishing (maintainers)
-
-```bash
-# 1. Bump version (semver)
-npm version patch  # or minor / major
-
-# 2. prepublishOnly chains: check-secrets → typecheck → rollup (clean + bundle + obfuscate + bundle check)
-npm publish
-```
-
-Pre-publish hooks:
-- `check-secrets` — scans for forbidden files (`.env`, `.pem`, `.key`) and provider-prefixed key strings (AWS / OpenAI / SendGrid / Google / GitHub / Slack / private-key blocks).
-- `typecheck` — `tsc --noEmit`.
-- `rollup` — produces `dist/index.js`, `dist/index.cjs`, `dist/index.d.ts`, `dist/styles.css`, then runs `scripts/obfuscate.js` and `scripts/check-bundle.js`.
-
-Inspect the publish tarball before pushing:
-
-```bash
-npm pack --dry-run
-```
-
-Only the contents of `dist/`, `README.md`, `LICENSE`, and `package.json` ship.
-
-## Versioning
-
-Strict semver:
-- **PATCH** — bug fixes, no API changes.
-- **MINOR** — additive features, no breakage.
-- **MAJOR** — breaking changes to `<Package />` props or `EditorHandle`.
-
 ## Author
 
 bitbeast private limited