Skip to content

Conversation

Lanhild
Copy link

@Lanhild Lanhild commented Dec 2, 2024

Add an automatic release workflow and conventional commits. The release workflow determines the
version from the type of commits and then links each commit to a changelog entry in the appropriate
section, according to the type of the latter.

A working example can be seen at https://github.com/Lanhild/pipelines on the main branch.

Before merging, a GitHub personal access token with write permissions has to be set in the actions secrets of the repository with the name TOKEN.

Add an automatic release workflow and conventional commits. The release workflow determines the
version from the type of commits and then links each commit to a changelog entry in the appropriate
section, according to the type of the latter.
BREAKING CHANGE: Temporarily change the repository URL of the package to test the build
@Lanhild
Copy link
Author

Lanhild commented Dec 2, 2024

Fixes #113

@ezavesky
Copy link
Contributor

ezavesky commented Jan 5, 2025

I had a similar need and ended up patching my own version with poetry and semantic-release actions. If we look at what was used for openwebui, there are hints that hatchling is the build chain of choice. In this pipelines repo, while there's no official versioning there is actually a mix of a few different tools, because in the Dockerfile there's a reference to the up-and-comer uv package tool.

Makes you appreciate the beauty and wants of a full volunteer/OSS effort, no? :)

@gunamata
Copy link

I see there's not much activity on this PR. Just wondering if there's some activity happening elsewhere on the release workflow for pipelines?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants