fix: make stratigraphic order consistent between methods and add unit test - #320
Merged
Conversation
…o-bump Neither package has a component-scoped release-please tag yet (they were only just added to the workspace in #301/#302), so release-please had no correct anchor for their next version and fell back to misreading one of the repo's old generic v1.6.5 LoopStructural tags as their baseline, proposing 1.6.5 for both in the open release PR instead of a proper minor bump from their real current versions (map2loop 3.3.1, loopstructuralvisualisation 0.1.17). One-time release-as pins to the correct next versions; remove once that release PR has merged and each package has its own release-please tag to anchor future bumps.
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.
No description provided.