@omnidist/omnidist 0.1.20 → 0.1.21

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.
Files changed (2) hide show
  1. package/README.md +32 -7
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -81,7 +81,15 @@ This creates:
81
81
  - `.omnidist/` workspace directories
82
82
  - `.omnidist/.gitignore` for generated artifacts
83
83
 
84
- 3. Build binaries for configured targets:
84
+ 3. Edit config and set environment variables (optional):
85
+
86
+ ```bash
87
+ $EDITOR .omnidist/omnidist.yaml
88
+ ```
89
+
90
+ `omnidist` loads `.env` automatically when present, so you can keep values like `OMNIDIST_VERSION`, `NPM_PUBLISH_TOKEN`, and `UV_PUBLISH_TOKEN` there.
91
+
92
+ 4. Build binaries for configured targets:
85
93
 
86
94
  ```bash
87
95
  omnidist build
@@ -89,7 +97,7 @@ omnidist build
89
97
 
90
98
  This also writes the resolved build version to `.omnidist/dist/VERSION`.
91
99
 
92
- 4. Stage and verify artifacts:
100
+ 5. Stage and verify artifacts:
93
101
 
94
102
  ```bash
95
103
  omnidist stage
@@ -100,18 +108,21 @@ omnidist verify
100
108
  `.omnidist/uv/pyproject.toml` with that version.
101
109
  It also recreates `.omnidist/uv/dist` to prevent stale wheel artifacts from previous runs.
102
110
 
103
- 5. Publish when verification passes:
111
+ 6. Publish when verification passes:
104
112
 
105
113
  ```bash
106
114
  omnidist publish
107
115
  ```
108
116
 
109
- 6. Generate tag-triggered release workflow:
117
+ 7. Generate tag-triggered release workflow:
110
118
 
111
119
  ```bash
112
120
  omnidist ci
113
121
  ```
114
122
 
123
+ The generated workflow publishes npm and uv artifacts and also creates a GitHub
124
+ release with the built cross-platform binaries plus `checksums.txt`.
125
+
115
126
  ## Common Commands
116
127
 
117
128
  ```bash
@@ -152,7 +163,7 @@ omnidist uv publish --publish-url https://test.pypi.org/legacy/ --token <pypi-to
152
163
 
153
164
  Supported variables:
154
165
 
155
- - `OMNIDIST_VERSION`: used when `version.source: env`; also expanded in `build.ldflags` templates (for example `${OMNIDIST_VERSION}`).
166
+ - `OMNIDIST_VERSION`: used only when `version.source: env`; also expanded in `build.ldflags` templates (for example `${OMNIDIST_VERSION}`).
156
167
  `VERSION` is not used.
157
168
  - `OMNIDIST_GIT_COMMIT`: optional ldflags template variable for build metadata; populated automatically by `omnidist build` when git metadata is available.
158
169
  - `OMNIDIST_BUILD_DATE`: optional ldflags template variable for build metadata; populated automatically by `omnidist build` as UTC RFC3339.
@@ -177,7 +188,9 @@ tool:
177
188
  main: ./cmd/omnidist
178
189
 
179
190
  version:
180
- source: git-tag # git-tag | file | env
191
+ source: git-tag # git-tag | file | env | fixed
192
+ file: VERSION # optional; used when source is file (default VERSION)
193
+ fixed: 1.2.3 # required when source is fixed
181
194
 
182
195
  targets:
183
196
  - os: darwin
@@ -201,6 +214,7 @@ distributions:
201
214
  package: "@omnidist/omnidist"
202
215
  registry: https://registry.npmjs.org
203
216
  access: public # public | restricted
217
+ license: MIT # optional override for package.json license; omit to use SEE LICENSE IN <file>
204
218
  include-readme: true # include project README.md in staged packages when present
205
219
 
206
220
  uv:
@@ -221,6 +235,16 @@ build:
221
235
 
222
236
  With `version.source: git-tag`, release workflows require `HEAD` to be on an exact SemVer tag (`vX.Y.Z` or `X.Y.Z`).
223
237
 
238
+ With `version.source: file`, omnidist reads `./VERSION` from the repository root.
239
+
240
+ With `version.source: file`, you can override the path via `version.file` (for example `versions/release.txt`).
241
+
242
+ With `version.source: fixed`, set `version.fixed` to an exact value in config (for example `1.2.3`).
243
+
244
+ With `version.source: env`, set `OMNIDIST_VERSION` (for example in `.env`) before build/stage/publish.
245
+
246
+ Use global `--omnidist-root <path>` to set the project root for a command. Omnidist resolves it to an absolute path at startup and changes working directory to it before loading `.env` and config.
247
+
224
248
  ## Command Reference
225
249
 
226
250
  Top-level:
@@ -290,7 +314,8 @@ omnidist ci
290
314
  ```
291
315
 
292
316
  The generated workflow triggers on `v*` tag pushes and runs:
293
- `build -> stage -> verify -> publish`.
317
+ `build -> stage -> verify -> publish`, then publishes the built binaries and
318
+ checksums to the GitHub release.
294
319
 
295
320
  If workflow already exists:
296
321
 
package/package.json CHANGED
@@ -14,11 +14,11 @@
14
14
  "license": "SEE LICENSE IN LICENSE",
15
15
  "name": "@omnidist/omnidist",
16
16
  "optionalDependencies": {
17
- "@omnidist/omnidist-darwin-arm64": "0.1.20",
18
- "@omnidist/omnidist-darwin-x64": "0.1.20",
19
- "@omnidist/omnidist-linux-arm64": "0.1.20",
20
- "@omnidist/omnidist-linux-x64": "0.1.20",
21
- "@omnidist/omnidist-win32-x64": "0.1.20"
17
+ "@omnidist/omnidist-darwin-arm64": "0.1.21",
18
+ "@omnidist/omnidist-darwin-x64": "0.1.21",
19
+ "@omnidist/omnidist-linux-arm64": "0.1.21",
20
+ "@omnidist/omnidist-linux-x64": "0.1.21",
21
+ "@omnidist/omnidist-win32-x64": "0.1.21"
22
22
  },
23
- "version": "0.1.20"
23
+ "version": "0.1.21"
24
24
  }