omnidist 0.1.42-aarch64-linux → 0.2.1-aarch64-linux

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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 8037a68739c59d4b8df00f529b751dfeed99ae8e7f8e3292c8adb2608543d173
4
- data.tar.gz: d6b1ecd000906340e3b2e90742b033a02ec2252855a3f81c306dd4344bbb9f6e
3
+ metadata.gz: 658c1e19eb0e5d9616a06cf592e5a545fc5f89dae19e62f1dacd2f9f4ec663fb
4
+ data.tar.gz: '01802820c54cfd1a08bd71a455bc00f89f043a91cb56bafba7556a99533dc07d'
5
5
  SHA512:
6
- metadata.gz: 42345c22ea39ce431215d7c798218a0611af7b71e8b18ce7d474fdcbf1e317c0ad0c32e38d635ed1f376d5cd9ee4c862a4afe91e5e74ad3133c1456287a65399
7
- data.tar.gz: bb457e7402ec4ec66a9e599e10f9af9ecf1a8af832361ed5f91c036d026de33ecdd261640e6507718e9f62c2654ddf42b5a61856362e578424736570804920bd
6
+ metadata.gz: 6bd37ddd3172287af86b937343342cfd13afd1d98dcf672376d9db55fde053003689d87c4e4f07b89aa7916ac0d0f65889dee18b2ed54d52a28c8f103c373eea
7
+ data.tar.gz: 8395b8a1bc4eea47f405f2acb173a31dde86a224706a2d4e8a9d96e69c84eafe35bda4006bc27a53e2dd275037b8dc42c7fdc917d7bb938b439c54af1f19b704
data/README.md CHANGED
@@ -26,13 +26,37 @@ Maintainers can also install from Go:
26
26
  go install github.com/metalagman/omnidist/cmd/omnidist@latest
27
27
  ```
28
28
 
29
+ ## Agent skill
30
+
31
+ The [Omnidist agent skill](skills/omnidist/SKILL.md) helps coding agents set up and run release workflows. Installing the skill adds agent instructions; install the Omnidist CLI separately using the commands above.
32
+
33
+ With Node.js and npm/npx available, run this from the project where you want to use the skill:
34
+
35
+ ```bash
36
+ npx skills add metalagman/omnidist --skill omnidist
37
+ ```
38
+
39
+ Installation is scoped to the current project by default; add `--global` to make the skill available across your projects:
40
+
41
+ ```bash
42
+ npx skills add metalagman/omnidist --skill omnidist --global
43
+ ```
44
+
45
+ The repository commands require the skill files to be published on GitHub. To install from a local checkout, including before publication, run this from the Omnidist repository root:
46
+
47
+ ```bash
48
+ npx skills add ./skills/omnidist --skill omnidist
49
+ ```
50
+
51
+ To check discovery without installing, use `npx skills add ./skills/omnidist --list`. See the [skills installer documentation](https://github.com/vercel-labs/skills#install-a-skill) for supported agents and options.
52
+
29
53
  ## Maintainer prerequisites
30
54
 
31
55
  | Activity | Required locally or in CI |
32
56
  | --- | --- |
33
57
  | Build the Go CLI | Go 1.25+; Git when `version.source: git-tag` |
34
58
  | npm stage/verify | Go build artifacts; npm is required at publish preflight/upload |
35
- | uv stage/verify/publish | `uv` |
59
+ | PyPI stage/verify/publish | `uv` |
36
60
  | gem stage/verify/publish | Ruby and RubyGems (`gem`) |
37
61
  | Token publish | The selected backend's token environment variable |
38
62
 
@@ -79,11 +103,11 @@ profiles:
79
103
  distributions:
80
104
  npm:
81
105
  package: "@my-org/mytool"
82
- uv:
106
+ pypi:
83
107
  package: mytool
84
108
  ```
85
109
 
86
- The `npm` and `uv` sections select those two backends. Add or remove `npm`, `uv`, and `gem` sections to define the canonical aggregate set. Existing files with a non-empty `enabled-distributions` selector remain readable, but every selected backend must have its own section. Aggregate commands always execute in npm → uv → gem order. `--only` can narrow the configured set but cannot enable an unavailable backend; backend-specific commands also require an explicit section.
110
+ The `npm` and `pypi` sections select those two backends. Add or remove `npm`, `pypi`, and `gem` sections to define the canonical aggregate set. Existing files with a non-empty `enabled-distributions` selector remain readable, but every selected backend must have its own section. Aggregate commands always execute in npm → pypi → gem order. `--only` can narrow the configured set but cannot enable an unavailable backend; backend-specific commands also require an explicit section.
87
111
 
88
112
  To offer both unscoped and scoped install names while publishing one shared platform package set, configure the unscoped package as primary, add the scoped name to `aliases`, and use the scoped base for platform packages:
89
113
 
@@ -133,6 +157,7 @@ The workflow contains setup, credentials, and publish jobs only for selected bac
133
157
  - [Release runbook](docs/releases.md) — credentials, first release, preflight, trusted publishing, and partial-release recovery.
134
158
  - [Targets and variants](docs/targets.md) — Go target values and npm/wheel/gem mappings.
135
159
  - [Contributing](CONTRIBUTING.md) — repository layout, tests, lint, and development workflow.
160
+ - [Omnidist agent skill](skills/omnidist/SKILL.md) — guidance for agents setting up and running release workflows.
136
161
 
137
162
  ## Commands
138
163
 
@@ -140,18 +165,18 @@ The workflow contains setup, credentials, and publish jobs only for selected bac
140
165
  omnidist init [--force] [--name <name>] [--main <package>]
141
166
  omnidist quickstart
142
167
  omnidist build
143
- omnidist stage [--dev] [--only npm,uv,gem]
144
- omnidist verify [--only npm,uv,gem]
145
- omnidist publish [--dry-run] [--only npm,uv,gem]
168
+ omnidist stage [--dev] [--only npm,pypi,gem]
169
+ omnidist verify [--only npm,pypi,gem]
170
+ omnidist publish [--dry-run] [--only npm,pypi,gem]
146
171
  omnidist ci [--force] [--dry-run]
147
172
  omnidist npm stage|verify|publish|trust
148
- omnidist uv stage|verify|publish
173
+ omnidist pypi stage|verify|publish
149
174
  omnidist gem stage|verify|publish
150
175
  ```
151
176
 
152
177
  Global flags are `--config`, `--profile`, and `--omnidist-root`. Omnidist also loads `.env`; corresponding selectors are `OMNIDIST_CONFIG`, `OMNIDIST_PROFILE`, and `OMNIDIST_OMNIDIST_ROOT`.
153
178
 
154
- Use `omnidist <command> --help` for backend-specific options.
179
+ Use `omnidist <command> --help` for backend-specific options. Earlier configuration, commands and environment variables remain supported; see [legacy compatibility](docs/configuration.md#legacy-compatibility).
155
180
 
156
181
  ## Common failures
157
182
 
data/libexec/omnidist CHANGED
Binary file
data/omnidist.gemspec CHANGED
@@ -1,6 +1,6 @@
1
1
  Gem::Specification.new do |spec|
2
2
  spec.name = "omnidist"
3
- spec.version = "0.1.42"
3
+ spec.version = "0.2.1"
4
4
  spec.summary = 'Build Go binaries and distribute them through npm, PyPI, and RubyGems'
5
5
  spec.description = 'Build Go binaries and distribute them through npm, PyPI, and RubyGems. Includes prebuilt binaries for the current platform.'
6
6
  spec.authors = ["omnidist"]
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: omnidist
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.42
4
+ version: 0.2.1
5
5
  platform: aarch64-linux
6
6
  authors:
7
7
  - omnidist