Skip to content

Release v6.3.1#1742

Draft
kdeldycke wants to merge 2 commits intomainfrom
prepare-release
Draft

Release v6.3.1#1742
kdeldycke wants to merge 2 commits intomainfrom
prepare-release

Conversation

@kdeldycke
Copy link
Copy Markdown
Owner

@kdeldycke kdeldycke commented Apr 9, 2026

Description

This PR is ready to be merged. See the prepare-release job documentation for details. The merge event will trigger the:

  1. Creation of a v6.3.1 tag on main branch

  2. Build and release of the Python package to PyPI

  3. Compilation of the project's binaries

  4. Publication of a GitHub v6.3.1 release with all artifacts above attached

How-to release v6.3.1

  1. Click Ready for review button below, to get this PR out of Draft mode

  2. Click Rebase and merge button below

Caution

Do not Squash and merge: we need the 2 distinct commits in this PR.

Important

If you suspect the PR content is outdated, click Run workflow to refresh it manually before merging.

Workflow metadata
Field Value
Trigger push
Actor @kdeldycke
Ref main
Commit f3115d56
Job prepare-release
Workflow changelog.yaml
Run #896.1

🏭 Generated with repomatic 6.11.2

@kdeldycke kdeldycke added the 🆙 changelog Affects the changelog label Apr 9, 2026
@kdeldycke kdeldycke self-assigned this Apr 9, 2026
@kdeldycke kdeldycke force-pushed the prepare-release branch 5 times, most recently from 98689fc to c1e0aa0 Compare April 10, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🆙 changelog Affects the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant