Bump version from 4.16.8 to 4.16.9 - #1264
Merged
robertatakenaka merged 1 commit intoJul 31, 2026
Merged
Conversation
This file contains hidden or 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
2 participants
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.
O que esse PR faz?
Atualiza
version.pyde4.16.8para4.16.9, preparando a próxima release. Desde a tag4.16.8(commit #1253), amasteracumulou correções sem bump de versão, entre elas:"text"emAbstract.datapub-date) em XMLWithPre e melhora sua atualização no XML #1262 — explicita defeitos em datas de publicação (pub-date) emXMLWithPreOnde a revisão poderia começar?
version.py(linha única alterada).Como este poderia ser testado manualmente?
Após o merge, confirmar que
packtools.__version__ == "4.16.9"e criar a tag4.16.9apontando para o commit de merge.Algum cenário de contexto que queira dar?
Optei por PATCH (4.16.9) em vez de MINOR, já que as mudanças pendentes desde a última tag são majoritariamente correções de bug; a leva de commits de i18n (#1257) já havia sido incluída antes da tag 4.16.8.
Quais são tickets relevantes?
Refs: #1261, #1262
Referências
N/A