@briangershon/publishable 0.1.1 → 0.1.3
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 +6 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -32,7 +32,12 @@ After merging latest code to main branch:
|
|
|
32
32
|
|
|
33
33
|
A GitHub release is automatically written and published to NPM.
|
|
34
34
|
|
|
35
|
-
**First-time setup:**
|
|
35
|
+
**First-time setup:**
|
|
36
|
+
|
|
37
|
+
1. Add `OPENROUTER_API_KEY` secret in GitHub repo Settings → Secrets and variables → Actions.
|
|
38
|
+
2. Run `npm login` locally and ensure you have access to the `@briangershon` scope.
|
|
39
|
+
3. Manually publish the package once to establish it on npm: `npm publish --access public`
|
|
40
|
+
4. Set up [npm Trusted Publishing](https://docs.npmjs.com/generating-provenance-statements) in your npm package settings to allow the GitHub Actions workflow to publish without a stored token.
|
|
36
41
|
|
|
37
42
|
## License
|
|
38
43
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@briangershon/publishable",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.3",
|
|
4
4
|
"description": "A tool for creating and managing content for publication.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -10,6 +10,7 @@
|
|
|
10
10
|
"dist"
|
|
11
11
|
],
|
|
12
12
|
"scripts": {
|
|
13
|
+
"prepublishOnly": "npm run build",
|
|
13
14
|
"build": "tsc && chmod +x dist/index.js",
|
|
14
15
|
"dev": "node --experimental-strip-types src/index.ts",
|
|
15
16
|
"start": "node dist/index.js"
|