Prepare 2.6.3 release - #316
Merged
Merged
Conversation
Drop the .dev4 suffix from the package version in pyproject.toml so that pushing the 2.6.3 tag publishes a final release to PyPI. The latest feature PRs (libigl bump + new bindings) will be merged into main and incorporated here before tagging. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alecjacobson
force-pushed
the
prepare-2.6.3-release
branch
from
August 31, 2026 17:07
fa40cbd to
7957492
Compare
Introduce CHANGELOG.md documenting the 2.6.3 release (folding in the tag-less interim 2.6.2 changes, i.e. everything since the last tagged release 2.6.1) and recording the new release process. This addresses the long-standing request for a changelog (#235). Also set generateReleaseNotes: true on the release-action step so each GitHub Release body is auto-populated with the merged PRs since the previous tag, instead of being empty. The curated highlights live in CHANGELOG.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alecjacobson
marked this pull request as ready for review
August 31, 2026 17:19
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
1 participant
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.
Draft / merging this to
maincuts the 2.6.3 release. Ready pending your go-ahead.Contents
pyproject.toml:2.6.3.dev5→2.6.3(this version change is the release trigger, per Publish to PyPI on a push to main that bumps the version #313).CHANGELOG.md(new): documents 2.6.3, folding in the tag-less interim 2.6.2 changes (i.e. everything since the last tagged release, 2.6.1). Addresses Changelog and git tag for 2.5.* #235.wheels.yml:generateReleaseNotes: trueon the release step so the GitHub Release body auto-lists merged PRs since the previous tag (it was empty before). Curated highlights stay inCHANGELOG.md.Rebased on current
main, so it already includes #314 (libigl →f68f01c2) and #315 (10 new bindings).Why the GitHub release will match PyPI this time
On a push to
mainthat changesproject.version,release_artifactsruns once from the samegithub.shaand (1) creates the git tag2.6.3+ GitHub Release (with wheels + sdist + auto notes) and (2) publishes those same artifacts to PyPI. Tag, release, and PyPI upload are produced together — fixing the 2.6.2 situation (PyPI-only, no tag; background in #301).Preconditions — ✅ met
libigl/libigl-python-bindings, workflowwheels.yml, environment "Any").To release
Merge this PR → the workflow tags
2.6.3, creates the GitHub release, and publishes to PyPI. Afterwards, bumpmainto2.6.4.dev0to resume development.Still open (optional)
2.6.2 remains on PyPI with no git tag / GitHub release. I can backfill a
2.6.2tag + release for historical consistency if you want.🤖 Generated with Claude Code