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

SDK: determine supported server versions automatically #7026

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

SpecLad
Copy link
Contributor

@SpecLad SpecLad commented Oct 18, 2023

Motivation and context

I think the spirit of the SUPPORTED_SERVER_VERSIONS constant is to allow the same and the next minor versions as the SDK, so just derive those versions automatically instead of bumping them every minor release.

How has this been tested?

I examined cvat_sdk.Client.SUPPORTED_SERVER_VERSIONS in the REPL.

Checklist

  • I submit my changes into the develop branch
  • [ ] I have created a changelog fragment
  • [ ] I have updated the documentation accordingly
  • [ ] I have added tests to cover my changes
  • [ ] I have linked related issues (see GitHub docs)
  • [ ] I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

I think the spirit of the `SUPPORTED_SERVER_VERSIONS` constant is to allow
the same and the next minor versions as the SDK, so just derive those
versions automatically instead of bumping them every minor release.
@SpecLad SpecLad requested a review from zhiltsov-max October 18, 2023 13:46
@codecov
Copy link

codecov bot commented Oct 18, 2023

Codecov Report

Merging #7026 (74993c5) into develop (e6724fa) will increase coverage by 0.04%.
Report is 10 commits behind head on develop.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##           develop    #7026      +/-   ##
===========================================
+ Coverage    82.31%   82.36%   +0.04%     
===========================================
  Files          361      361              
  Lines        39168    39168              
  Branches      3586     3586              
===========================================
+ Hits         32243    32259      +16     
+ Misses        6925     6909      -16     
Components Coverage Δ
cvat-ui 77.36% <ø> (+0.08%) ⬆️
cvat-server 86.95% <80.00%> (ø)

Copy link
Contributor

@zhiltsov-max zhiltsov-max left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the spirit of the SUPPORTED_SERVER_VERSIONS constant is to allow the same and the next minor versions as the SDK

It was never supposed to be like this - the variable is literally the list of supported versions for each SDK release. But we can surely add this change to simplify maintenance of new releases, as it reflects our current strategy.

@SpecLad
Copy link
Contributor Author

SpecLad commented Oct 19, 2023

It was never supposed to be like this - the variable is literally the list of supported versions for each SDK release.

Okay, I'm going to remove this part from the commit message.

@SpecLad SpecLad merged commit 9004b27 into cvat-ai:develop Oct 19, 2023
@SpecLad SpecLad deleted the auto-supported-versions branch October 19, 2023 10:30
mikhail-treskin pushed a commit to retailnext/cvat that referenced this pull request Oct 25, 2023
This removes what should be the last manual step that used to be involved
in making a release.
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.

2 participants