@bensandee/tooling 0.84.3 → 0.85.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.
Files changed (4) hide show
  1. package/README.md +4 -0
  2. package/dist/bin.mjs +816 -95
  3. package/package.json +1 -1
  4. package/tooling.schema.json +2 -2
package/README.md CHANGED
@@ -477,6 +477,10 @@ Tags generated per package: `latest`, `vX.Y.Z` (or `vX.Y.Z-<pre>` for a prerelea
477
477
 
478
478
  A prerelease version (`1.2.3-beta.0`) pushes only its own exact tag, which keeps the suffix -- `v1.2.3-beta.0` -- and moves no floating tag; each skipped ref is logged with that reason. Otherwise a floating tag moves forward only: `docker:publish` leaves `latest`, `vX` or `vX.Y` where the registry has it whenever that version is newer than the one being published.
479
479
 
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
+
482
+ `--dry-run` reads no registry, so the tag list it prints is a plan for records as well as floating tags.
483
+
480
484
  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.
481
485
 
482
486
  **Flags:** `--dry-run` (build and tag only, skip login/push/logout), `--verbose`