Repository navigation
Version 1.6.0 - #119
Merged
Merged
Version 1.6.0#119
Conversation
The changelog section of the changes since 1.5.9 becomes 1.6.0, dated 2026-10-18, with its comparison link, and __version__ is 1.6.0. It is a minor version: periodic microstructures and other features are added, with no change to the existing interface beyond those in the changelog. The example digest of the documentation is updated, since the package changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kip-hart
approved these changes
Oct 19, 2026
kip-hart
left a comment
kip-hart
left a comment
Owner
There was a problem hiding this comment.
This looks good to me, thanks! I was planning on doing this so thanks for saving me from this step. I'll still have to tag and release on GitHub. Fortunately I can use the existing releases as a guide since it's been a while!
Collaborator
Author
|
Fantastic!! Glad it works! We continue to use microstructpy extensively!
|
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.
Sets the version to 1.6.0, to release what is on develop.
__version__is 1.6.0.setup.pyand the docs read it from there.1.6.0 - 2026-10-18, with its comparison link, like the 1.5.9 entry. If the release happens on another day, the date is a one-line change.EXAMPLES_DIGESTis updated, since the package changed.It is a minor version, since periodic microstructures and other features are added.
The plan, if you agree: once this is merged, I merge #114 into master with a merge commit. It picks this up, and your approval stays. A merge commit keeps the history of develop in master, so later develop-to-master PRs stay clean. Then a GitHub release tagged v1.6.0 on master runs your publish workflow, which uploads to PyPI. Since the package on PyPI is yours, would you like to create the release yourself, or should I?
Checked locally: the source distribution builds as microstructpy-1.6.0 and passes
setup.py check, check-manifest and twine, and a nitpicky docs build has no warnings.🤖 Generated with Claude Code