Skip to content

change the versioning method to that of the template repo#951

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

change the versioning method to that of the template repo#951
walshmm merged 2 commits intonextfrom
migrate_version_to_current_template_method

Conversation

@walshmm
Copy link
Contributor

@walshmm walshmm commented Dec 8, 2025

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 force-pushed the migrate_version_to_current_template_method branch from c80e7bc to 70776a0 Compare January 29, 2026 14:22
@walshmm walshmm merged commit 00f17cd into next Jan 29, 2026
6 checks passed
@walshmm walshmm deleted the migrate_version_to_current_template_method branch January 29, 2026 14:30
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