@bensandee/tooling 0.99.0 → 0.100.0
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 +6 -2
- package/dist/bin.mjs +963 -871
- package/package.json +4 -4
- package/tooling.schema.json +1 -1
package/README.md
CHANGED
|
@@ -403,7 +403,7 @@ The trimmed record's `packages` map is computed by aggregating files whose path
|
|
|
403
403
|
|
|
404
404
|
Docker packages are discovered automatically. Any package with a `Dockerfile` or `docker/Dockerfile` is a Docker package. Image names are derived as `{root-package-name}-{package-name}`, build context defaults to `.` (project root). For single-package repos, `Dockerfile` or `docker/Dockerfile` at the project root is checked.
|
|
405
405
|
|
|
406
|
-
With `publishDocker` set, the release workflow publishes Docker images after
|
|
406
|
+
With `publishDocker` set, the release workflow publishes Docker images after a release, for the images whose version it bumped. To publish by hand, run `bst docker:publish` with the registry credentials. `repo:sync` archives a managed `publish.yml` left by older versions.
|
|
407
407
|
|
|
408
408
|
#### Overrides
|
|
409
409
|
|
|
@@ -479,11 +479,15 @@ A prerelease version (`1.2.3-beta.0`) pushes only its own exact tag, which keeps
|
|
|
479
479
|
|
|
480
480
|
The exact `vX.Y.Z` tag is that version's record, and it is pushed only when the registry does not have it. A run that finds it there keeps it -- nothing from that run's build is published under the version -- and points any floating tag that is behind, unlabelled or unparsable at that record with `docker buildx imagetools create`, so a floating tag never names content different from the record it is meant to point at. No flag pushes over a record: new content under an unchanged version means bumping the enclosing package, or editing that image's `version` override.
|
|
481
481
|
|
|
482
|
+
Under the `changesets` release strategy, an image is pushed only when the release commit (HEAD) changed the version in the file it takes its version from -- its `.tooling.json#docker` `version` override, the enclosing `packages/<name>/package.json`, or the root `package.json`. An image whose version is an explicit `version` override is never bounded: an override moves by a hand edit, which is never a release commit, so a rule keyed on it would never publish the image at all. `release:simple`, `release-it` and `none` are unchanged, because those strategies bump files the images may not read and would stop publishing them for good. Every image is still **built**, bounded or not, since a bumped image can build `FROM` an unbumped one. The skipped images are counted in the run's summary and named one per line.
|
|
483
|
+
|
|
484
|
+
That leaves one recovery for a bump commit whose Release step passed and whose Docker step failed: a job rerun does not reach the Docker step, so run `bst docker:publish` by hand with HEAD at that bump commit, where HEAD is the bump. `--image <name>` is the other door -- it publishes the named images with no bound and skips every other, for an image whose package simply never bumps.
|
|
485
|
+
|
|
482
486
|
`--dry-run` reads no registry, so the tag list it prints is a plan for records as well as floating tags.
|
|
483
487
|
|
|
484
488
|
Each package is tagged independently using its own version, so packages in a monorepo can have different release cadences. Packages without a `version` field are rejected at publish time.
|
|
485
489
|
|
|
486
|
-
**Flags:** `--dry-run` (build and tag only, skip login/push/logout), `--verbose`
|
|
490
|
+
**Flags:** `--dry-run` (build and tag only, skip login/push/logout), `--image <name>` (publish only this image, by its final image name, without the release bound; repeatable), `--verbose`
|
|
487
491
|
|
|
488
492
|
**Required CI variables:**
|
|
489
493
|
|