Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.1.0 🎉 #57

Merged
merged 27 commits into from
Nov 1, 2024
Merged

Release 1.1.0 🎉 #57

merged 27 commits into from
Nov 1, 2024

Conversation

lbeckman314
Copy link
Member

Includes all updates made to the release-1.1.0 branch, including support for TES v1.1

uniqueg and others added 10 commits February 9, 2023 23:43
feat: spec-compliant suffixes, with legacy support
* test: increase unit test coverage

* Update tests.yml

---------

Co-authored-by: Liam Beckman <lbeckman314@gmail.com>
* docs: browsable API reference on GitHub Pages

* Update tests.yml

---------

Co-authored-by: Liam Beckman <lbeckman314@gmail.com>
@lbeckman314 lbeckman314 mentioned this pull request Jan 18, 2024
@lbeckman314 lbeckman314 self-assigned this Jan 18, 2024
@uniqueg
Copy link
Collaborator

uniqueg commented Jan 22, 2024

Awesome, Liam 🚀

I'm curious (but too lazy/busy to dive into the code): Is py-tes 1.1.0 backwards-compatible with TES 1.0.0 servers? And is there are general policy how client/server compatibility will be handled for py-tes (e.g. extra code, different branches, only maintaining support for latest server version)? Might be good to include some info on this in the docs.

@github-pages github-pages bot temporarily deployed to github-pages February 1, 2024 22:41 Inactive
- Fix version to match PyPi release (#59)
@lbeckman314
Copy link
Member Author

lbeckman314 commented Feb 29, 2024

Hi Alex! Apologies for the astronomically late reply — backwards-compatibility with TES 1.1.0 servers is definitely something that we should ensure prior to this release, with steps for handling different versions being added to the documentation like you recommend.

Whether that support is from extra code or handled different branches is still a question to be answered.

Having the version support be on different branches is perhaps the quickest/easiest way in the short term, with maybe a long-term goal of having this be configurable both on the command line and within the tes module (manually by the user or automatically by querying the server).

I've just created a new issue for this (#60) to track the progress on this. Please add any thoughts or suggestions on this compatibility support and we'll go from there! 🚀

@vsmalladi
Copy link
Collaborator

@lbeckman314 is this released yet?

@lbeckman314 lbeckman314 merged commit f2e6909 into master Nov 1, 2024
6 checks passed
@lbeckman314 lbeckman314 deleted the release-1.1.0 branch November 1, 2024 20:02
@lbeckman314
Copy link
Member Author

@vsmalladi Yes! Apologies for the delay — updating the GitHub release and docs today and will update here when complete 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants