You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ci(version-check): require uv.lock sync alongside pyproject changes
Resolves CE-202. Mirrors the workflow + script changes from
socket-python-cli#204 so the SDK catches lockfile drift the same way
the CLI now does:
- workflow: trigger paths drop unused setup.py, add uv.lock; new step
fails CI if pyproject.toml is modified without uv.lock.
- sync_version.py: new run_uv_lock() helper runs 'uv lock' and signals
whether the lockfile changed. Wired into all three exit paths
(--dev auto-bump, normal auto-bump, already-bumped) so the hook
either updates uv.lock for you or tells you to commit it.
* ci(version-check): also require PR version > latest PyPI stable
Mirrors socket-python-cli's fix at 0462b77 (in PR #199). The workflow
previously only compared the PR version against main, which missed
the case where the same or newer version had already been published
to PyPI — that would slip through CI and either collide on publish
or leave PyPI ahead of the repo.
- workflow: hits pypi.org/pypi/socketdev/json, filters to stable
(non-prerelease, non-devrelease), requires PR > max(main, PyPI).
- sync_version.py: splits PYPI_PROD_API vs PYPI_TEST_API. Stable
auto-bumps now use prod PyPI as the floor via
find_next_stable_patch_version(). The .devN flow keeps using
TestPyPI. New 'already bumped but ≤ PyPI' path auto-corrects the
version when somebody bumps to a stale number.
0 commit comments