Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,5 @@
# Changelog

## [0.3.2](https://github.com/syntasso/kratix-python/compare/v0.3.0...v0.3.2) (2025-11-23)


### Chores

* setting python 3.10 as minimum required version
* configuring application for release
* exposing version in the package


## [0.3.0](https://github.com/syntasso/kratix-python/compare/v0.2.0...v0.3.0) (2025-10-29)


Expand Down
7 changes: 4 additions & 3 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,10 @@ This document captures the steps for cutting a new version of the SDK and publis
Alternatively export `POETRY_HTTP_BASIC_TESTPYPI_USERNAME="__token__"` and `POETRY_HTTP_BASIC_TESTPYPI_PASSWORD="<token>"` before publishing.

2. **Prep the repo**
- Update `pyproject.toml` with the new version under `[tool.poetry]`.
- Add an entry to `CHANGELOG.md` summarising the release and changes.
- Commit your work before building artifacts.
- Prior to pypi release, release-please has to manage / generate a new version number.
- All commits should be merged to `main`.
- Once release-please has created a PR, merge it to `main` with the new version number in `pyproject.toml` .
- Pull down the latest `main` branch.

3. **Run quality checks**
```bash
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "poetry.core.masonry.api"

[tool.poetry]
name = "kratix-sdk"
version = "0.3.2"
version = "0.3.0"
description = "Kratix SDK for writing Promises workflows"
readme = "Readme.md"
authors = ["Syntasso <[email protected]>"]
Expand Down