release: bump to 0.4.3 so the next PyPI release ships as Apache-2.0 - #61
Merged
Conversation
PyPI 0.4.2 was published before the relicense merged and carries MIT metadata; PyPI versions are immutable, so the current 0.4.2 cannot be re-published as Apache-2.0. Bump to 0.4.3 (first Apache-2.0 release) and correct the historical notes: releases up to and including 0.4.2 were MIT; Apache-2.0 applies from 0.4.3. Verified the 0.4.3 wheel metadata reads 'License: Apache License' and twine check passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0149fLyfQuAaxNRfoPGoyf2x
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
2 participants
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.
Why
You asked whether the repo is ready to ship Apache-2.0. It wasn't quite: PyPI
0.4.2was published before the relicense (#60) merged, so that artifact carries MIT metadata (License: MIT License … Copyright (c) 2024 heidihelena). PyPI versions are immutable, somainat0.4.2cannot be re-published as Apache-2.0 — a version bump is required.Changes
pyproject.toml→version = "0.4.3"(first Apache-2.0 release).CITATION.cff→version: 0.4.3,date-released: 2026-07-12.NOTICEand README License note → corrected to say releases up to and including0.4.2were MIT, and Apache-2.0 applies from0.4.3onward. (Previously they said only0.4.1.)Verification
python -m build→vahtian_epinet-0.4.3; wheel metadata readsLicense: Apache LicensewithLicense-File: LICENSE+NOTICE.twine checkPASSED (both sdist + wheel).CITATION.cffparses as valid YAML.After merge — how the release ships as Apache-2.0
Cut a GitHub Release for
v0.4.3(or run the Publish workflow manually). Thepublish.ymlfix (#55) means it fires once and uploads0.4.3via Trusted Publishing — the first release carrying the Apache-2.0 license.🤖 Generated with Claude Code
Generated by Claude Code