@yudin-s/react-chrome-ai 0.1.0 → 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 +10 -0
- package/docs/publishing.md +18 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.2
|
|
4
|
+
|
|
5
|
+
- Publish release artifacts to GitHub Packages in addition to npmjs.com.
|
|
6
|
+
- Keep package contents and public API unchanged from `0.1.1`.
|
|
7
|
+
|
|
8
|
+
## 0.1.1
|
|
9
|
+
|
|
10
|
+
- Validate GitHub Actions trusted publishing release flow.
|
|
11
|
+
- Keep package contents and public API unchanged from `0.1.0`.
|
|
12
|
+
|
|
3
13
|
## 0.1.0
|
|
4
14
|
|
|
5
15
|
- Initial React hooks for Chrome Built-in AI `LanguageModel`.
|
package/docs/publishing.md
CHANGED
|
@@ -72,9 +72,24 @@ 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 to npmjs.com and GitHub Packages.
|
|
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`.
|
|
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.
|
|
78
93
|
|
|
79
94
|
### Manual First Publish
|
|
80
95
|
|