@gerdloos/npm-trusts-github-skill 1.0.0 → 1.0.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/.github/workflows/publish.yml +1 -1
- package/README.md +12 -1
- package/package.json +10 -3
package/README.md
CHANGED
|
@@ -1,7 +1,18 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Sets up the npm-trusts-github skill
|
|
2
|
+
|
|
3
|
+
> ⚠️ **ALPHA SOFTWARE** — This package is under active development.
|
|
4
|
+
> APIs, skill structure, and behavior may change without notice.
|
|
2
5
|
|
|
3
6
|
A skill that teaches an LLM how to set up npm trusted publishing (OIDC) with GitHub Actions.
|
|
4
7
|
|
|
8
|
+
Provide knowledge to the llm to setup npm, github and auth so a new version triggers publication on npm.
|
|
9
|
+
|
|
10
|
+
I myself for now prefer github private, and the npm instance is the public one.
|
|
11
|
+
|
|
12
|
+
At the moment in alpha, it's more about setting up from fresh, first time use focused.
|
|
13
|
+
|
|
14
|
+
Not yet atm : LLM should create a "publish to npm"-guideline folder or doc per project, with in it project specifics, then reference the guideline per project.
|
|
15
|
+
|
|
5
16
|
## Install on Pi
|
|
6
17
|
|
|
7
18
|
```bash
|
package/package.json
CHANGED
|
@@ -1,10 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gerdloos/npm-trusts-github-skill",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"description": "A skill that teaches an LLM how to set up npm trusted publishing with GitHub Actions",
|
|
5
|
-
"keywords": [
|
|
5
|
+
"keywords": [
|
|
6
|
+
"pi-package",
|
|
7
|
+
"npm",
|
|
8
|
+
"publish",
|
|
9
|
+
"workflow"
|
|
10
|
+
],
|
|
6
11
|
"license": "MIT",
|
|
7
12
|
"pi": {
|
|
8
|
-
"skills": [
|
|
13
|
+
"skills": [
|
|
14
|
+
"./skills"
|
|
15
|
+
]
|
|
9
16
|
}
|
|
10
17
|
}
|