Publishing

Once your module passes all quality gates and the CI pipeline is green, you can publish it to PyPI. Publishing is automated through the CI pipeline — you just need to push a version tag.

Prerequisites

Before publishing, ensure:

• All quality gates pass (uv run plesty check)
• The CI pipeline is green on the exp branch
• CHANGELOG.md is updated with the new version
• pyproject.toml has the correct version number

Version numbering

PLESTY follows semantic versioning:

v<major>.<minor>.<patch>

Publishing workflow

Step 1: Update the version

Update the version in pyproject.toml:

[project]
name = "plesty-my-device"
version = "0.3.0"

Step 2: Update the changelog

Add an entry to CHANGELOG.md:

## [0.3.0] - 2026-07-22

### Added
- New measurement mode for continuous acquisition
- Support for remote calibration

### Fixed
- Timeout handling on slow connections

Step 3: Commit and push

git add pyproject.toml CHANGELOG.md
git commit -m "chore: bump version to 0.3.0"
git push origin feat/bump-version:exp

Step 4: Tag and push the tag

git tag v0.3.0
git push origin v0.3.0

Pushing a v* tag triggers the release stage in the CI pipeline, which builds the package and publishes it to PyPI.

What happens in CI

When a v* tag is pushed:

1. Gate 14 triggers the build and release job
2. The package is built (sdist + wheel)
3. The package is published to PyPI
4. A GitLab release is created

Verifying the release

After the pipeline completes:

1. Check that the package is on PyPI: https://pypi.org/project/plesty-my-device/
2. Verify the GitLab release is created
3. Test installing the package: uv pip install plesty-my-device

Troubleshooting

Next steps

• Review the CI pipeline configuration
• Explore the quality gates reference