Release 2.23.0 #679
Release 2.23.0 #679
Conversation
|
@gabrielilharco FYI I don't think merging release via PR triggers a release @rom1504 ... at least it didn't last time. Also, might want to wait until the nltk thing is fixed up as this will push it into an active release... |
|
@rwightman sgtm, we can wait for the nice SigLIP+CLIPA PR and do a big one. As for the trigger, maybe it depends on how the PR is merged? Seems to work for Squash and merge at least (e.g. #511) |
|
It does trigger a release as long as the commit is named "Release X.Y.Z" |
|
What about merging the ntlk thing before the big clippa/siglip is merged? It would not hurt to have some people use the current state of the repo, just in case anything is wrong |
|
@rom1504 it'd be entirely separate fix that I'd have to ignore on the SigLIP PR on merge as I refactored the tokenizers to get rid of the singleton. Someone else is welcome to do that. |
|
Ok if it's not trivial then I guess let's wait |
* Release 2.23.0 * Update HISTORY.md
Closes #678