@yudin-s/react-chrome-ai 0.1.1 → 0.1.2
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/CHANGELOG.md +5 -0
- package/docs/publishing.md +3 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/docs/publishing.md
CHANGED
|
@@ -75,7 +75,7 @@ Suggested flow:
|
|
|
75
75
|
2. Publish the first package version manually if the package does not exist yet.
|
|
76
76
|
3. Configure npm trusted publishing for the package and release workflow.
|
|
77
77
|
4. Tag a release, for example `v0.1.1`.
|
|
78
|
-
5. Let GitHub Actions publish
|
|
78
|
+
5. Let GitHub Actions publish to npmjs.com and GitHub Packages.
|
|
79
79
|
|
|
80
80
|
Trusted publishing requires npm CLI `11.5.1` or later and Node `22.14.0` or later. The publish workflow uses Node `24`.
|
|
81
81
|
|
|
@@ -89,6 +89,8 @@ Configure npm trusted publishing with:
|
|
|
89
89
|
|
|
90
90
|
When published through trusted publishing from this public GitHub repository, npm automatically generates provenance attestations. The workflow does not need `--provenance`.
|
|
91
91
|
|
|
92
|
+
The same workflow also publishes the package to GitHub Packages using `GITHUB_TOKEN` and the `packages: write` permission. The GitHub Packages step sets `NPM_CONFIG_PROVENANCE=false` because GitHub Packages is authenticated with `GITHUB_TOKEN`, while npmjs.com provenance is handled by trusted publishing.
|
|
93
|
+
|
|
92
94
|
### Manual First Publish
|
|
93
95
|
|
|
94
96
|
If publishing manually:
|