insightfactory-cli 1.0.0.dev4__py3-none-any.whl → 1.0.1.dev6__py3-none-any.whl

{insightfactory_cli-1.0.0.dev4.dist-info → insightfactory_cli-1.0.1.dev6.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: insightfactory-cli
-Version: 1.0.0.dev4
+Version: 1.0.1.dev6
 Summary: Profile-based authentication CLI for the InsightFactory Interfaces API
 Project-URL: Homepage, https://github.com/insightfactory-ai/insightfactory-cli
 Project-URL: Repository, https://github.com/insightfactory-ai/insightfactory-cli
@@ -212,12 +212,16 @@ Python 3.10 or newer is required. Runtime code is stdlib-only.
 
 ## Release
 
-Publishing is automatic from GitHub Actions on merge. Verify and build live in
-the reusable workflow
+**A release is cut by pushing a tag, not by merging.** Merging to `main` runs CI and
+publishes nothing.
+
+```bash
+git tag v1.0.1 && git push origin v1.0.1
+```
+
+Verify and build live in the reusable workflow
 [`if_s_insightfactory_cli.yml`](https://github.com/insightfactory-ai/if_sre_github_actions/blob/main/.github/workflows/if_s_insightfactory_cli.yml)
-in `insightfactory-ai/if_sre_github_actions`
-([PR #300](https://github.com/insightfactory-ai/if_sre_github_actions/pull/300)
-must merge before these stubs go green). This repository's
+in `insightfactory-ai/if_sre_github_actions`. This repository's
 `.github/workflows/release.yml` keeps only the OIDC publish job, because PyPI
 Trusted Publishing is registered for **this** repo, workflow `release.yml`, and
 environment `pypi` — a reusable workflow cannot be registered.
@@ -228,24 +232,38 @@ the reusable workflow and uploads it with `pypa/gh-action-pypi-publish`.
 
 | Trigger | Published version | PyPI role |
 |---|---|---|
-| Push / merge to `develop` | `1.0.0.dev{N}` | pre-release (`pip install --pre`) |
-| Push / merge to `main` | `1.0.0` (the version in `pyproject.toml`) | latest |
-| Push of a `v*` tag | same as `main` | retry / explicit cut of that version |
+| Push / merge to `develop` | `1.0.1.dev{N}` | pre-release (`pip install --pre`) |
+| Push of a `v*` tag | the version in `pyproject.toml`, which the tag must match | latest |
+| Merge to `main` | nothing — CI only | — |
 
 `N` is `github.run_number` of the reusable workflow: a per-workflow integer
 that goes up on every run and stays the same across re-runs of that run (so a
 failed publish can be retried under the same version). It does not depend on
-git history or clone depth. After a successful `main` publish, bump `version`
-in `pyproject.toml` on `develop` so later `.devN` builds sort *after* what just
-landed; PEP 440 puts `1.0.0.devN` before `1.0.0`. Because of that ordering, a
+git history or clone depth. After a successful release, bump `version` in
+`pyproject.toml` on `develop` so later `.devN` builds sort *after* what just
+landed; PEP 440 puts `1.0.1.devN` before `1.0.1`. Because of that ordering, a
 dependency spec of `insightfactory-cli>=1.0.0` does not match develop-channel
 `.devN` builds; an in-process consumer that wants them must specify a
 pre-release-bearing spec such as `insightfactory-cli>=1.0.0.dev0` (which also
 matches the final `1.0.0` release).
 
-A version that is already on PyPI is skipped rather than failing, so a second
-push to `main` (or a `v*` tag for the same version) is a no-op. A `v*` tag
-whose name does not match `pyproject.toml` fails before publishing.
+A `v*` tag whose name does not match `pyproject.toml` fails before publishing.
+
+The two channels treat an already-published version differently, on purpose:
+
+- **Release channel (a tag):** publishing fails, naming the fix. A tag is a request to
+  release that version; if it cannot be honoured, the run must say so rather than report
+  success having published nothing. (git also refuses to push a tag that already exists,
+  so this is hard to reach.)
+- **Dev channel (`develop`):** publishing is skipped quietly. `.dev{N}` uses
+  `github.run_number`, which is stable across re-runs of one run, so an already-present
+  version there can only mean a re-run of a run that already published — real idempotency,
+  not a swallowed mistake.
+
+This split is why releasing moved off `main`. While a merge was the trigger, an
+already-published version *had* to be tolerated as a no-op for merges to stay green — so a
+merge that released nothing looked exactly like one that released, and a forgotten version
+bump shipped nothing silently.
 
 ## Differences from the Node CLI
 

{insightfactory_cli-1.0.0.dev4.dist-info → insightfactory_cli-1.0.1.dev6.dist-info}/RECORD

@@ -17,7 +17,7 @@ if_cli/commands/logout.py,sha256=TW0P4_tXcTtiHHR73xVPHyhlbOWD1jBnkZsMImCiCBw,668
 if_cli/commands/profiles.py,sha256=JNBrYWdHQ9MHauwZxH33IAOYgRYRniX7bwd7KBT6Vyk,3869
 if_cli/commands/set_token.py,sha256=BVyv_QmByvllr04pE2sz8JFEscHbIgOC-7ZPg61PRoc,1886
 if_cli/commands/token.py,sha256=CyiXkyH7vxgH91-n-XJzeHnLI6mZJwO9Js5AHvfHaeM,1120
-insightfactory_cli-1.0.0.dev4.dist-info/METADATA,sha256=YpQzgahIWH3aVL5DIyLLgKd31VnwKYjNGdZAJM8mUwQ,10880
-insightfactory_cli-1.0.0.dev4.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
-insightfactory_cli-1.0.0.dev4.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
-insightfactory_cli-1.0.0.dev4.dist-info/RECORD,,
+insightfactory_cli-1.0.1.dev6.dist-info/METADATA,sha256=Bk1mnRW48Ac7z7Ir5pTTKS6QC-TOEQpyuvcUcC0h9Iw,11651
+insightfactory_cli-1.0.1.dev6.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+insightfactory_cli-1.0.1.dev6.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
+insightfactory_cli-1.0.1.dev6.dist-info/RECORD,,