[fix] Always override the originally saved __version__ in the ST config
#2709
Conversation
This file contains 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
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.
Hello!
Pull Request overview
Details
Currently, the
__version__data is only determines once, and then all future models finetuned on that model will just adopt the original versions. This can become a problem as e.g. ST v3.0 will save models that have e.g. "2.2.2" in their configuration, which is rather confusing.Example
E.g. https://huggingface.co/ammumadhu/indic-bert-nli-matryoshka/blob/main/config_sentence_transformers.json
which shows 2.2.2 whereas the model itself was trained with v3.0.0.
cc @osanseviero