@woovi/ui 6.9.6 → 6.9.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +37 -0
- package/dist/index.cjs +1 -1
- package/dist/index.js +1 -1
- package/package.json +8 -13
package/README.md
CHANGED
|
@@ -73,6 +73,43 @@ function App() {
|
|
|
73
73
|
- React 18.3.1 or higher
|
|
74
74
|
- React DOM 18.3.1 or higher
|
|
75
75
|
|
|
76
|
+
## Publishing
|
|
77
|
+
|
|
78
|
+
`@woovi/ui` is published to **two** registries, and both must stay in sync:
|
|
79
|
+
|
|
80
|
+
| Registry | Why it matters |
|
|
81
|
+
| --- | --- |
|
|
82
|
+
| [`registry.npmjs.org`](https://registry.npmjs.org) | Public consumers. |
|
|
83
|
+
| [`verdaccio.woovi.dev`](https://verdaccio.woovi.dev) | In-house registry that **all Woovi CI** installs from. The `@woovi/*` scope is **not** proxied to npm (dependency-confusion protection), so a version that only reaches public npm is invisible in CI and breaks `pnpm install` with `ERR_PNPM_FETCH_404`. |
|
|
84
|
+
|
|
85
|
+
Two scripts handle this, both **idempotent** — they check the target registry first and skip if the current `package.json` version is already published:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
# Publish the public release (manual / local only — needs your own `npm login`)
|
|
89
|
+
pnpm publish:npm
|
|
90
|
+
|
|
91
|
+
# Publish to the in-house Verdaccio (run locally, and also done automatically by CI)
|
|
92
|
+
pnpm publish:verdaccio
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
### Release checklist
|
|
96
|
+
|
|
97
|
+
1. Bump the version (`pnpm release:patch` / `release:minor` / `release:major`).
|
|
98
|
+
2. `pnpm publish:npm` — publishes to public npm.
|
|
99
|
+
3. `pnpm publish:verdaccio` — publishes the same version to Verdaccio (or let CI do it on the next staging deploy).
|
|
100
|
+
|
|
101
|
+
> **Don't skip step 3.** Publishing to npm alone leaves Verdaccio behind and breaks every downstream Woovi CI pipeline that depends on the new version.
|
|
102
|
+
|
|
103
|
+
### CI
|
|
104
|
+
|
|
105
|
+
The `tekton-woovi-ui` staging pipeline runs `pnpm publish:verdaccio` automatically (task `task-publish-verdaccio-app`, after `build`). It is **Verdaccio-only** — no npm automation token is provisioned in-cluster, so the public npm publish stays a manual step. Because the script is idempotent, re-running the pipeline on an already-published version is a no-op.
|
|
106
|
+
|
|
107
|
+
### Auth
|
|
108
|
+
|
|
109
|
+
- **npm:** `npm login` (your own account) before `pnpm publish:npm`.
|
|
110
|
+
- **Verdaccio (local):** `npm login --registry https://verdaccio.woovi.dev` (Google SSO).
|
|
111
|
+
- **Verdaccio (CI):** the Tekton task writes `~/.npmrc` from the Verdaccio publish token; nothing to do.
|
|
112
|
+
|
|
76
113
|
## License
|
|
77
114
|
|
|
78
115
|
MIT
|