insightfactory-cli 1.1.1.dev25__py3-none-any.whl → 1.1.2.dev28__py3-none-any.whl

{insightfactory_cli-1.1.1.dev25.dist-info → insightfactory_cli-1.1.2.dev28.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: insightfactory-cli
-Version: 1.1.1.dev25
+Version: 1.1.2.dev28
 Summary: Profile-based authentication CLI for the InsightFactory Interfaces API
 Project-URL: Homepage, https://insightfactory.ai
 Author-email: "insightfactory.ai Support" <support@insightfactory.ai>
@@ -354,20 +354,32 @@ artifact, so its notes belong on that Release. A checkout with no tags falls bac
 to the tagged version's section alone.
 
 `develop` therefore carries the version the next release will use, and the
-`release-guard` job holds it there. A PR into `develop` must raise `version` in
-`pyproject.toml` above what `develop` already has, and must add that version's
-`CHANGELOG.md` section. `tools/check_release.py` runs both checks and is what
-fails the PR:
+`release-guard` job holds it there. `tools/check_release.py` runs the checks and
+is what fails the PR:
 
 ```bash
-BASE=origin/develop python3 tools/check_release.py
+BASE=origin/develop RELEASED=origin/main python3 tools/check_release.py
 ```
 
-One version per PR, then. The instinct is to let a second change join the
-section the first one opened, and the guard refuses that: the version would be
-tagged with notes that do not describe everything in it, and nothing stops the
-tag going out between the two merges. Bump the patch number again, or fold the
-second change into the first PR.
+**Every PR into `develop` adds a `CHANGELOG.md` entry.** That is the whole point
+of the file, and a change with no entry reaches users with no line anywhere
+saying it happened.
+
+**The version moves once per release cycle, not once per PR.** The first PR after
+a release raises `version` in `pyproject.toml` and opens that version's section;
+the rest of the cycle adds to the section it opened. The guard asks for the bump
+only while `develop` is still on the version `main` is on, because that version
+is released and its notes describe something your change is not in.
+
+The comparison is against `main` rather than against the tag, which matters in
+the window where the release PR has merged but the tag is not pushed yet. What a
+version contains is fixed when it reaches `main`, so a change landing after that
+belongs to the next version, whatever the tags say.
+
+A PR into `main` always needs the bump. It carries no new entries, only the
+version they were written under, and `main` exists to be tagged: leaving it on
+`main`'s own version makes it un-taggable, since that version is on PyPI and any
+other tag matches no file.
 
 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)

{insightfactory_cli-1.1.1.dev25.dist-info → insightfactory_cli-1.1.2.dev28.dist-info}/RECORD

@@ -27,8 +27,8 @@ if_cli/router/log.py,sha256=YLWeHUb05HUnS3XHubCwy7oLZAUEGAiHcZysz_YMAAo,412
 if_cli/router/policy.py,sha256=CclbjuOA5mwwoQiNDa17iQeN9eXRbfy11bS9JFd8gL4,2840
 if_cli/router/server.py,sha256=RkS6Ddann-vAU0ZQAe2QaEB9dLBvEC33V9O-G4WSIy8,12116
 if_cli/router/upstream.py,sha256=dmwS7qSLnHiY7dEYpVENkfYIHs3DxkhhMB1SV66lE2Y,13104
-insightfactory_cli-1.1.1.dev25.dist-info/METADATA,sha256=MhOT9TEnUHIqQLtN7W1dgVT0KJrHc7H3CHbLBV_XE9g,19502
-insightfactory_cli-1.1.1.dev25.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
-insightfactory_cli-1.1.1.dev25.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
-insightfactory_cli-1.1.1.dev25.dist-info/licenses/LICENSE,sha256=8eZ1YAABL398qESVJc_FlK1voYQ0GAh-R_rNBQK6QH8,234
-insightfactory_cli-1.1.1.dev25.dist-info/RECORD,,
+insightfactory_cli-1.1.2.dev28.dist-info/METADATA,sha256=lrvEqTY6PVwH8Y0TZJXWSJ2XGiDsDaYE9l7oMM3sk0w,20159
+insightfactory_cli-1.1.2.dev28.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+insightfactory_cli-1.1.2.dev28.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
+insightfactory_cli-1.1.2.dev28.dist-info/licenses/LICENSE,sha256=8eZ1YAABL398qESVJc_FlK1voYQ0GAh-R_rNBQK6QH8,234
+insightfactory_cli-1.1.2.dev28.dist-info/RECORD,,