Skip to content

Update versioning to not replace incorrectly#958

Merged
walshmm merged 2 commits intonextfrom
update_versioning_to_not_replace_incorrectly
Jan 29, 2026
Merged

Update versioning to not replace incorrectly#958
walshmm merged 2 commits intonextfrom
update_versioning_to_not_replace_incorrectly

Conversation

@walshmm
Copy link
Contributor

@walshmm walshmm commented Jan 29, 2026

Short description of the changes:

Long description of the changes:

Check list for the pull request

  • I have read the [CONTRIBUTING]
  • I have read the [CODE_OF_CONDUCT]
  • I have added tests for my changes
  • I have updated the documentation accordingly

Check list for the reviewer

  • I have read the [CONTRIBUTING]
  • I have verified the proposed changes
  • best software practices
    • all internal functions have an underbar, as is python standard
    • clearly named variables (better to be verbose in variable names)
    • code comments explaining the intent of code blocks
  • All the tests are passing
  • The documentation is up to date
  • code comments added when explaining intent

Manual test for the reviewer

References

@walshmm walshmm merged commit fb04e24 into next Jan 29, 2026
5 checks passed
@walshmm walshmm deleted the update_versioning_to_not_replace_incorrectly branch January 29, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant