ci: add conventional commit check and release please#1356
Merged
vincentsarago merged 12 commits intomainfrom Mar 31, 2026
Merged
ci: add conventional commit check and release please#1356vincentsarago merged 12 commits intomainfrom
vincentsarago merged 12 commits intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'TiTiler performance Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.30.
| Benchmark suite | Current: f21acad | Previous: 4b5f858 | Ratio |
|---|---|---|---|
WebMercator response_time |
0.03 s |
0.02 s |
1.50 |
WGS1984Quad response_time |
0.04 s |
0.03 s |
1.33 |
This comment was automatically generated by workflow using github-action-benchmark.
…-conventional-commit-check-and-release-please
lhoupert
commented
Mar 30, 2026
| The Helm chart (`deployment/k8s/charts/`) is versioned independently from the Python package. release-please opens a separate helm release PR when commits touch files under `deployment/k8s/charts/`. That PR bumps `version:` in `Chart.yaml` and updates `deployment/k8s/charts/CHANGELOG.md`. The resulting GitHub release is tagged `helm-vX.Y.Z`. | ||
|
|
||
| 5. Push your release branch, create a PR, and get approval | ||
| **Commit messages matter for chart releases.** A chart version bump only happens when a commit both: |
vincentsarago
approved these changes
Mar 31, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch tightens release automation on `main` with Release Please, adds enforced conventional commits in CI and optionally via pre-commit (commit-msg), and documents the workflow for contributors. It also includes follow-up CI fixes, chart/version alignment for release automation, and dependency lock updates.
What changed
Conventional commits
.github/workflows/commitlint.ymlruns on every push (all branches) and validates commits in the pushed range with Commitizen (cz check), usinguv runwith a pinnedcommitizen==4.13.9..pre-commit-config.yaml: commitizen hook on thecommit-msgstage so invalid messages can be blocked locally after developers runpre-commit install --hook-type commit-msg.Release Please + PyPI
.github/workflows/release.yml: on push tomain, Release Please opens/manages release PRs (usesrelease-please-config.jsonand.release-please-manifest.json). Onrelease: published, the workflow builds artifacts and publishes to PyPI with OIDC trusted publishing (pypa/gh-action-pypi-publish).CHANGES.md, GitHub style), version bumps for rootpyproject.toml, all subpackage__init__.py/pyproject.tomlextras, LambdaDockerfile, and HelmChart.yaml(appVersion).Helm chart independent versioning
release-please-config.json: the Helm chart (deployment/k8s/charts/) is registered as a separate release-please package (release-type: helm). Itsversion:field inChart.yamlis bumped independently from the Python package, driven by conventional commits that touch files underdeployment/k8s/charts/. Helm releases are taggedhelm-vX.Y.Z.deployment/k8s/charts/CHANGELOG.md: created as the changelog file required by thehelmrelease type..release-please-manifest.json: tracks the chart version (2.1.1) separately from the Python package version (2.0.0).Docs & housekeeping
RELEASING.md: fully rewritten to reflect the automated release process; replaces the old manual checklist with a description of the release-please flow, the independent helm chart release flow, and the commit convention table.CONTRIBUTING.md: guidance updated for the new commit/release expectations.pyproject.toml/ package versions and chart/lambda metadata adjusted so Release Please can keep them in sync;uv.lockrefreshed..github/workflows/check_charts.yaml.Notes for reviewers
commit-msg) is installed; CI still enforces on push.main, confirm Release Please app/permissions and PyPI trusted publisher settings match this workflow.version:and the Python package version are intentionally independent: the chart only gets a new release when commits touchdeployment/k8s/charts/. TheappVersion:inChart.yaml(which controls the default image tag) continues to track the Python package version automatically.