Skip to content

v1.0.0b1: CI/CD pipeline

Pre-release
Pre-release

Choose a tag to compare

@mathys-lopinto mathys-lopinto released this 15 Apr 12:01
· 97 commits to master since this release
e3b43c6

Tabby Sync Version 1.0.0 - Beta 1

First beta. Leaving alpha now that a real CI/CD pipeline protects the code and the published image is built on every tag.

Highlights

Continuous integration

A GitHub Actions workflow runs on every push and every pull request targeting master. Ruff lint, Ruff format check, and the full pytest suite with branch coverage all have to pass before anything merges. Coverage is uploaded to Codecov and surfaced through the badge in the README.

Published Docker image

Every v*.*.* git tag now triggers a second workflow that builds the Dockerfile and publishes ghcr.io/mathys-lopinto/tabby-sync with semver tags. Pre-release tags (alpha, beta, rc) get their own versioned tag but leave :latest alone, so pulling :latest always lands on a stable release.

The base docker-compose.yml now ships with a commented image: line next to build: ., so operators can swap one for the other to pull the published image instead of building locally.

Dependabot

Weekly pull requests for dependency bumps across Poetry, the Docker base image and the GitHub Actions used in the workflows. Patch and minor updates are grouped to reduce PR noise.

Ruff hygiene

A first pass of ruff check and ruff format on the existing code added a __str__ to Config, cleaned up a duplicate import and an unused variable in the test suite, and kept null=True on two Tabby-client-populated CharFields (User.active_version, Config.last_used_with_version) as a documented ignore since the stored representation is part of the client contract.

Image

docker pull ghcr.io/mathys-lopinto/tabby-sync:1.0.0b1

Or open docker-compose.yml and uncomment the image: line to pull instead of building.

Upgrade notes

  • No migration added since alpha3. Existing users, tokens and configs are untouched.
  • Enable branch protection on master so the new CI / lint-and-test status check gates merges. Recommended rules: require a PR, require the CI status check to pass, require linear history, require conversation resolution.