chore: bump version to 1.8.0 - #65
Conversation
Release bump for the v1.8.0 tag. Two changes have landed since v1.7.0: - #62 chore: refresh the dev apache-airflow lock to clear security alerts (dev dependency group only, no runtime surface change) - #64 feat: emit the X-Wherobots-Client attribution header (WBC-819) The attribution header is additive and reads the provider version from the installed distribution metadata, so this bump is what makes the provider report `client=airflow;ver=1.8.0` — minor, not patch, because #64 adds behavior. No runtime dependency floors change; wherobots-python-dbapi stays at >=0.28.0, and the published 0.28.1 already carries the `extra_headers` support the header relies on. Version lives in two places, both updated: `pyproject.toml` and the `airflow-providers-wherobots` entry in `uv.lock`. `uv lock --locked` passes, so no other lock churn was needed.
![salty-hambot[bot]](https://avatars.githubusercontent.com/in/2952321?s=60&v=4){kind=small}
There was a problem hiding this comment.
Reviewed by Salty Hambot 🤖🧂 — rubric mode
Verdict: ✅ pass
| Dimension | Verdict | Notes |
|---|---|---|
| correctness | ✅ pass | Single version string change, syntactically valid TOML. |
| security | ✅ pass | No security surface touched by a version bump. |
| privacy | ✅ pass | No data handling changes. |
| reliability | ✅ pass | Version metadata only; no runtime behavior affected. |
| scalability | ✅ pass | No performance or scaling implications. |
| observability | ✅ pass | No logging or metrics changes needed. |
| clarity/maintainability | ✅ pass | Clear, minimal, self-explanatory change. |
| test quality | ✅ pass | Version bump requires no test changes. |
Just a version bump from 1.7.0 to 1.8.0 — nothing to see here, ship it.
0 finding(s) posted.
💰 Review cost: $0.1070 · 29.6k in / 422 out tokens · ⏱️ 16.2s
💬 To request a re-review, comment @salty-hambot review
|
@peterfoldes (cc @sfishel18) — review needed on head Release bump for the
Those are the only two places this package declares its version — there's no Minor rather than patch because #64 (X-Wherobots-Client attribution header) is additive; #62 touched only the dev group. Full reasoning is in the PR description, along with two things I deliberately left alone (stale The |
3 participants
What
Bumps the package version
1.7.0→1.8.0ahead of thev1.8.0release tag. Version-only — no code, dependency, or workflow changes.pyproject.toml[project].version1.7.0→1.8.0uv.lockairflow-providers-wherobotsself-entry1.7.0→1.8.0These are the only two places this package's version is declared. There is no
__version__attribute: the runtime value is derived viaimportlib.metadata.version()inclient_attribution.py, which both theX-Wherobots-Clientheader and the REST hook's User-Agent read from.uv lock --lockedpasses, so no further lock churn was needed.Why 1.8.0 (minor)
Two commits have landed since
v1.7.0:chore: refresh the devapache-airflowlock to clear security alerts. Dev dependency group only; the published wheel still depends solely onwherobots-python-dbapiandpydantic, so no public-surface effect.feat: emit theX-Wherobots-Clientattribution header (WBC-819). Purely additive: a new module plus a new outbound header on both hooks. No signatures changed or removed, and it degrades silently on drivers withoutextra_headers.Additive behavior, nothing broken and nothing merely fixed — minor, not patch or major.
wherobots-python-dbapiv0.28.1 (shipped 2026-08-10) already carries theextra_headerssupport the header relies on, and the runtime floor stays at>=0.28.0, so there is no ordering constraint against the driver release.This bump is also what makes the provider actually report itself: after it, the emitted header is
client=airflow;ver=1.8.0(verified locally).Out of scope, noted for follow-up
client_attribution.pyhasver=1.7.0inside a module docstring and an inline comment. Both are illustrative examples of the header format — not a version source — and the paireddbapi;ver=0.28.1half would drift regardless. Left alone deliberately; the durable fix is genericizing them tover=<version>, which is its own change.CONTRIBUTING.mdstep 1 still says to edit[tool.poetry].version. That key has not existed since the hatchling + uv migration; the correct location is[project].version, which this PR edits. Steps 2–4 (tag, push tag, CI validates) are still accurate.Verification
uv run pytest tests/unit_tests— 51 passed.uv lock --locked— passes, lock consistent withpyproject.toml.uv run python -c "...client_attribution_header()"→{'X-Wherobots-Client': 'client=airflow;ver=1.8.0'}.Release note
The
v1.8.0tag is not pushed by this PR.pypi-publish.yamlfires on av[0-9]+.[0-9]+.[0-9]+tag push and validatesuv versionagainst the tag name — that comparison resolves to1.8.0once this merges. Tagging is a separate step after merge.