Uh oh!
There was an error while loading. Please reload this page.
chore: release master - #313
Merged
Merged
Conversation
lachlangrose
commented
Aug 14, 2026
Member
Do not merge — release-please picked the wrong tag-naming baseline (looking for |
4 tasks
github-actionsBotforce-pushed
the
release-please--branches--master
branch
from
August 14, 2026 06:56
89f2897 to
69d9541CompareUh oh!
There was an error while loading. Please reload this page.
3 tasks
lachlangrose added a commit
that referenced
this pull request
Aug 14, 2026
#314 deleted this file, but the release-please run triggered by that same merge re-created it with __version__ = "1.7.2" (LoopStructural's version, not loop_interpolation's real "0.0.1") before PR #313 was merged. Its own filename-search log line still showed the file as found on that run -- most likely GitHub's code-search index hadn't caught up with the deletion commit yet. Root cause: pointing the LoopStructural component's path at "." makes release-please's "find any file named version.py" search genuinely repo-wide rather than scoped to LoopStructural/, so it can collide with any version.py anywhere in the tree, present or future (e.g. the still-unmerged map2loop/loopstructural_visualisation packages each have their own). There's no release-please config to scope that search to a subpath, so the durable fix is having no other version.py files left for it to find. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
1 task
rolandhill pushed a commit
to rolandhill/LoopStructural
that referenced
this pull request
Aug 26, 2026
…mponent Repointing the LoopStructural component's path to "." (in Loop3D#312) let release-please discover its component name from pyproject.toml, which flipped it to the manifest-mode default of prefixing tags with the component name (LoopStructural-v*). No such tags exist -- every past release used a plain v* tag -- so release-please couldn't find the real last release and fell back to an ancient v1.6.5 tag as its baseline, computing a regressive "next version" of 1.6.5 in PR Loop3D#313. include-component-in-tag: false restores the historical plain v* tag scheme so release-please finds v1.7.1 as the last release again. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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 freeto 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.
🤖 I have created a release beepboop
1.7.2
1.7.2 (2026-08-14)
Bug Fixes
This PR was generated with Release Please. See documentation.