konecty-sdk-python 2.1.0__tar.gz → 2.1.1__tar.gz

{konecty_sdk_python-2.1.0 → konecty_sdk_python-2.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: konecty_sdk_python
-Version: 2.1.0
+Version: 2.1.1
 Summary: Konecty SDK Python
 Author-email: Leonardo Leal <leonardo.leal@konecty.com>, Derotino Silveira <derotino.silveira@konecty.com>
 License: MIT
@@ -127,9 +127,29 @@ uv pip install -e ".[dev]"
 
 #### Build & Publish
 
-It is needed to increase the version number on the [pyproject](./pyproject.toml) file.
+Publishing runs from the **Publish** workflow, triggered by hand from the Actions tab
+(`Run workflow`) — no merge publishes on its own. Pick the increment (`patch`, `minor` or
+`major`) and run it; **the version bump is part of publishing**, so there is nothing to edit
+beforehand.
+
+The workflow runs the tests, bumps `version` in [pyproject.toml](./pyproject.toml), builds into
+`dist-build/` and uploads with `uv publish` (secret `PYPI_API_TOKEN`). Only after the upload
+succeeds does it commit `chore(release): <version>` and tag it — a failed upload leaves no bump
+behind claiming a release that does not exist on PyPI.
+
+<details>
+<summary>Publishing manually</summary>
+
+Same PyPI endpoint (`upload.pypi.org/legacy/`) and the same kind of API token. Credentials
+come from `.pypirc`, which is gitignored and therefore local-only — this is why CI
+authenticates through a secret instead.
 
 ```sh
 uv build
 uvx twine upload --config-file .pypirc --skip-existing dist/*
 ```
+
+Note `--skip-existing`: unlike the workflow, this silently skips versions already published,
+and it is what keeps a stale local `dist/` from re-uploading old artifacts.
+
+</details>

{konecty_sdk_python-2.1.0 → konecty_sdk_python-2.1.1}/README.md

@@ -97,9 +97,29 @@ uv pip install -e ".[dev]"
 
 #### Build & Publish
 
-It is needed to increase the version number on the [pyproject](./pyproject.toml) file.
+Publishing runs from the **Publish** workflow, triggered by hand from the Actions tab
+(`Run workflow`) — no merge publishes on its own. Pick the increment (`patch`, `minor` or
+`major`) and run it; **the version bump is part of publishing**, so there is nothing to edit
+beforehand.
+
+The workflow runs the tests, bumps `version` in [pyproject.toml](./pyproject.toml), builds into
+`dist-build/` and uploads with `uv publish` (secret `PYPI_API_TOKEN`). Only after the upload
+succeeds does it commit `chore(release): <version>` and tag it — a failed upload leaves no bump
+behind claiming a release that does not exist on PyPI.
+
+<details>
+<summary>Publishing manually</summary>
+
+Same PyPI endpoint (`upload.pypi.org/legacy/`) and the same kind of API token. Credentials
+come from `.pypirc`, which is gitignored and therefore local-only — this is why CI
+authenticates through a secret instead.
 
 ```sh
 uv build
 uvx twine upload --config-file .pypirc --skip-existing dist/*
 ```
+
+Note `--skip-existing`: unlike the workflow, this silently skips versions already published,
+and it is what keeps a stale local `dist/` from re-uploading old artifacts.
+
+</details>

{konecty_sdk_python-2.1.0 → konecty_sdk_python-2.1.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "konecty_sdk_python"
-version = "2.1.0"
+version = "2.1.1"
 description = "Konecty SDK Python"
 readme = "README.md"
 requires-python = ">=3.11"