@segmentify/ui 1.0.0 → 1.0.1

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.
Files changed (3) hide show
  1. package/README.md +5 -10
  2. package/dist/ui.css +1222 -2360
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -72,26 +72,21 @@ Package-owned portaled content establishes `ui-lib-root` automatically. Consumer
72
72
  - `pnpm build-storybook`: Build the Storybook documentation.
73
73
  - `pnpm lint`: Run ESLint to check for code quality issues.
74
74
  - `pnpm format`: Format the codebase using Prettier.
75
- - `pnpm release`: Publish the package using Changesets.
75
+ - `pnpm release`: Publish the package using Changesets (run by the `Release` workflow).
76
76
 
77
77
  ## Releasing
78
78
 
79
- This project uses Changesets for versioning and releases.
79
+ This project uses Changesets for versioning and releases. Publishing runs in GitHub Actions through npm trusted publishing, so no npm token is needed on your machine or in the repository secrets.
80
80
 
81
81
  ### Configuration
82
82
 
83
- To publish new releases, you must have an `.npmrc` file in the root of the project with a valid npm authToken:
84
-
85
- ```text
86
- @segmentify:registry=https://registry.npmjs.org/
87
- //registry.npmjs.org/:_authToken=YOUR_NPM_AUTH_TOKEN
88
- ```
83
+ `@segmentify/ui` has a trusted publisher on npmjs.com (package settings → Trusted publishing) pointing to GitHub Actions, repository `segmentify-frontend/segmentify-ui`, workflow `release.yml`. If the workflow file is renamed, update the trusted publisher as well.
89
84
 
90
85
  ### Process
91
86
 
92
87
  1. **Create a Changeset**: Run `pnpm changeset` and follow the prompts to document your changes.
93
- 2. **Version Packages**: Run `pnpm version-packages` to update versions and the changelog.
94
- 3. **Publish**: Run `pnpm release` to publish the new version to npm.
88
+ 2. **Version Packages**: Run `pnpm version-packages` to update versions and the changelog, then merge the change to `main`.
89
+ 3. **Publish**: On every push to `main`, the `Release` workflow builds the package and runs `pnpm release`, which publishes any version that is not yet on npm.
95
90
 
96
91
  ## License
97
92