Repository navigation
v1.0.0b2: fix PEP 440 release pipeline and bump deps
Pre-releaseTabby Sync Version 1.0.0 - Beta 2
Re-issue of v1.0.0b1 with a working release pipeline, plus a first Dependabot round.
Why this release
v1.0.0b1 merged and tagged, but docker/metadata-action's type=semver silently rejected the PEP 440 version, so only :latest was published and no versioned tag made it to GHCR. Worse, that :latest actually pointed at the beta image because the pre-release gate looked for the literal word beta, not the PEP 440 b.
This release exercises the fixed workflow and publishes the image correctly.
What changed since b1
Release workflow
release.ymlnow usestype=matchto extract the version from the tag name, handling both PEP 440 (1.0.0b2) and semver (1.0.0-beta1) forms.major.minoris only applied to stable tags.latestis gated on the absence ofa,bandrcsubstrings, so pre-releases never touch it.
Dependencies
First Dependabot run, grouped under the python-minor update:
- psycopg 3.2.10 → 3.3.3
- ruff 0.11.13 → 0.15.10
No breaking changes touch this project; the pin-in-version strategy caught by poetry.lock keeps the install reproducible.
Application code
No changes. The Django app, CLI commands and admin flows are identical to b1.
Image
docker pull ghcr.io/mathys-lopinto/tabby-sync:1.0.0b2No :latest or :1.0 tag for this pre-release.
Housekeeping
The stale :latest image left over from the b1 run has been manually deleted from the GHCR package UI — the workflow does not rewrite it.