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
uv run pytest --cov titiler.stacapi --cov-report term-missing
18
22
```
19
23
20
24
This repo is set to use `pre-commit` to run *isort*, *flake8*, *pydocstring*, *black* ("uncompromising Python code formatter") and mypy when committing new code.
21
25
22
26
```bash
23
-
$ pre-commit install
27
+
uv run pre-commit install
28
+
29
+
# If needed, you can run pre-commit script manually
This is a checklist for releasing a new version of **titiler-stacapi**.
4
+
5
+
1. Create a release branch named `release/vX.Y.Z`, where `X.Y.Z` is the new version
6
+
7
+
2. Make sure the [Changelog](CHANGES.md) is up to date with latest changes and release date set
8
+
9
+
3. Run [`bump-my-version`](https://callowayproject.github.io/bump-my-version/) to update all titiler's module versions:
10
+
11
+
```
12
+
bump-my-version bump minor --new-version 0.20.0
13
+
```
14
+
15
+
4. Push your release branch, create a PR, and get approval
16
+
17
+
5. Once the PR is merged, create a new (annotated, signed) tag on the appropriate commit. Name the tag `X.Y.Z`, and include `vX.Y.Z` as its annotation message
18
+
19
+
```
20
+
git tag vX.Y.Z
21
+
```
22
+
23
+
6. Push your tag to Github, which will kick off the publishing workflow
24
+
25
+
7. Create a [new release](https://github.com/developmentseed/titiler-stacapi/releases/new) targeting the new tag, and use the "Generate release notes" feature to populate the description. Publish the release and mark it as the latest
0 commit comments