@adviser/ovn-fabric 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/README.md +7 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -120,11 +120,13 @@ an explanation of what it's for and why it's shaped the way it is.
|
|
|
120
120
|
|
|
121
121
|
## Publishing (maintainers)
|
|
122
122
|
|
|
123
|
-
|
|
124
|
-
`
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
123
|
+
`package.json`/`deno.json` carry a `0.0.0` placeholder version in git — there's
|
|
124
|
+
nothing to bump by hand. Tag a commit `vX.Y.Z` and push it; CI derives the
|
|
125
|
+
version from that tag, patches it into both files, then publishes to npm and
|
|
126
|
+
JSR via OIDC trusted publishing (see `.github/workflows/ci.yaml` and
|
|
127
|
+
`scripts/patch-version.mjs`; no token secrets involved, but it does require a
|
|
128
|
+
one-time registry-side setup — see the comment at the top of that workflow
|
|
129
|
+
file).
|
|
128
130
|
|
|
129
131
|
## License
|
|
130
132
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adviser/ovn-fabric",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Declarative OVN/OVS topology generator — one config, one self-installing shell script per host.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"publishConfig": {
|
|
@@ -35,4 +35,4 @@
|
|
|
35
35
|
"dependencies": {
|
|
36
36
|
"deno": "^2.9.1"
|
|
37
37
|
}
|
|
38
|
-
}
|
|
38
|
+
}
|