@omnidist/omnidist-linux-x64 0.1.22 → 0.1.24

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 CHANGED
@@ -79,7 +79,10 @@ omnidist init
79
79
  This creates:
80
80
  - `.omnidist/omnidist.yaml`
81
81
  - `.omnidist/` workspace directories
82
- - `.omnidist/.gitignore` for generated artifacts
82
+
83
+ `omnidist init` writes profiles-mode config with a `default` profile.
84
+ It also derives default `distributions.npm.package` / `distributions.uv.package`
85
+ from the current directory name (slugified).
83
86
 
84
87
  3. Edit config and set environment variables (optional):
85
88
 
@@ -95,7 +98,8 @@ $EDITOR .omnidist/omnidist.yaml
95
98
  omnidist build
96
99
  ```
97
100
 
98
- This also writes the resolved build version to `.omnidist/dist/VERSION`.
101
+ This also writes the resolved build version to `.omnidist/<profile>/dist/VERSION`
102
+ (`.omnidist/default/dist/VERSION` with init defaults).
99
103
 
100
104
  5. Stage and verify artifacts:
101
105
 
@@ -105,8 +109,9 @@ omnidist verify
105
109
  ```
106
110
 
107
111
  `omnidist uv stage` converts the resolved version to PEP 440 and writes
108
- `.omnidist/uv/pyproject.toml` with that version.
109
- It also recreates `.omnidist/uv/dist` to prevent stale wheel artifacts from previous runs.
112
+ `.omnidist/<profile>/uv/pyproject.toml` with that version.
113
+ It also recreates `.omnidist/<profile>/uv/dist` to prevent stale wheel artifacts from previous runs.
114
+ On first stage run, omnidist creates `.omnidist/.gitignore` (if missing).
110
115
 
111
116
  6. Publish when verification passes:
112
117
 
@@ -186,6 +191,9 @@ UV_PUBLISH_TOKEN=pypi-xxx
186
191
 
187
192
  `.omnidist/omnidist.yaml`:
188
193
 
194
+ `omnidist init` now generates the profiles-mode shape (`profiles.default`) by default.
195
+ Legacy top-level format remains supported when loading config files.
196
+
189
197
  ```yaml
190
198
  tool:
191
199
  name: omnidist
@@ -196,6 +204,8 @@ version:
196
204
  file: VERSION # optional; used when source is file (default VERSION)
197
205
  fixed: 1.2.3 # required when source is fixed
198
206
 
207
+ readme-path: docs/README.md # optional shared README source for staging
208
+
199
209
  targets:
200
210
  - os: darwin
201
211
  arch: amd64
@@ -219,12 +229,14 @@ distributions:
219
229
  registry: https://registry.npmjs.org
220
230
  access: public # public | restricted
221
231
  license: MIT # optional override for package.json license; omit to use SEE LICENSE IN <file>
232
+ readme-path: docs/npm-readme.md # optional npm-specific README source
222
233
  include-readme: true # include project README.md in staged packages when present
223
234
 
224
235
  uv:
225
236
  package: omnidist
226
237
  index-url: https://upload.pypi.org/legacy/
227
238
  linux-tag: manylinux2014 # manylinux2014 | musllinux_1_2
239
+ readme-path: docs/uv-readme.md # optional uv-specific README source
228
240
  include-readme: true # include project README.md in staged wheels when present
229
241
  ```
230
242
 
@@ -238,6 +250,7 @@ profiles:
238
250
  main: ./cmd/omnidist
239
251
  version:
240
252
  source: env
253
+ readme-path: docs/README.md
241
254
  targets:
242
255
  - os: linux
243
256
  arch: amd64
@@ -248,8 +261,10 @@ profiles:
248
261
  distributions:
249
262
  npm:
250
263
  package: "@scope/mytool"
264
+ readme-path: docs/npm-readme.md
251
265
  uv:
252
266
  package: mytool
267
+ readme-path: docs/uv-readme.md
253
268
 
254
269
  release:
255
270
  tool:
@@ -273,6 +288,10 @@ Mixing top-level runtime fields and `profiles` in the same file is not supported
273
288
 
274
289
  `targets` use Go values (`GOOS`/`GOARCH`). Distribution workflows map them as needed (for example `windows/amd64` -> npm `win32/x64`).
275
290
 
291
+ README source precedence during staging:
292
+ `distributions.<name>.readme-path` -> `readme-path` -> `README.md`.
293
+ If a configured readme-path is set and cannot be read, staging fails.
294
+
276
295
  For appkit version injection, configure `build.ldflags` in your project config:
277
296
 
278
297
  ```yaml
@@ -280,6 +299,9 @@ build:
280
299
  ldflags: -s -w -X github.com/metalagman/appkit/version.version=${OMNIDIST_VERSION} -X github.com/metalagman/appkit/version.gitCommit=${OMNIDIST_GIT_COMMIT} -X github.com/metalagman/appkit/version.buildDate=${OMNIDIST_BUILD_DATE}
281
300
  ```
282
301
 
302
+ `build.ldflags` values are expanded with `os.ExpandEnv` during `omnidist build`.
303
+ Both `${VAR}` and `$VAR` are supported; unset vars expand to empty strings.
304
+
283
305
  With `version.source: git-tag`, release workflows require `HEAD` to be on an exact SemVer tag (`vX.Y.Z` or `X.Y.Z`).
284
306
 
285
307
  With `version.source: file`, omnidist reads `./VERSION` from the repository root.
package/bin/omnidist CHANGED
Binary file
package/package.json CHANGED
@@ -16,5 +16,5 @@
16
16
  "os": [
17
17
  "linux"
18
18
  ],
19
- "version": "0.1.22"
19
+ "version": "0.1.24"
20
20
  }