@yudin-s/react-chrome-ai 0.1.0 → 0.1.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.
- package/CHANGELOG.md +5 -0
- package/docs/publishing.md +16 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/docs/publishing.md
CHANGED
|
@@ -72,9 +72,22 @@ Benefits:
|
|
|
72
72
|
Suggested flow:
|
|
73
73
|
|
|
74
74
|
1. Create the GitHub repository matching `package.json`.
|
|
75
|
-
2.
|
|
76
|
-
3.
|
|
77
|
-
4.
|
|
75
|
+
2. Publish the first package version manually if the package does not exist yet.
|
|
76
|
+
3. Configure npm trusted publishing for the package and release workflow.
|
|
77
|
+
4. Tag a release, for example `v0.1.1`.
|
|
78
|
+
5. Let GitHub Actions publish with `npm publish --access public`.
|
|
79
|
+
|
|
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
|
+
|
|
82
|
+
Configure npm trusted publishing with:
|
|
83
|
+
|
|
84
|
+
- Provider: GitHub Actions
|
|
85
|
+
- Organization or user: `yudin-s`
|
|
86
|
+
- Repository: `react-chrome-ai`
|
|
87
|
+
- Workflow filename: `publish.yml`
|
|
88
|
+
- Environment: leave empty unless a GitHub deployment environment is added later
|
|
89
|
+
|
|
90
|
+
When published through trusted publishing from this public GitHub repository, npm automatically generates provenance attestations. The workflow does not need `--provenance`.
|
|
78
91
|
|
|
79
92
|
### Manual First Publish
|
|
80
93
|
|