Repository navigation
chore: prepara release 3.3.16 - #626
Merged
regyssilveira merged 1 commit intoOct 29, 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
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.
Prepara a versão 3.3.16, alinhando
boss.json.versioneHORSE_VERSION.Inclui a correção do keep-alive dos providers Indy no Linux (#624): opções nativas em segundos evitam Socket Error #22 com Indy antigo e preservam compatibilidade com Indy moderno. O Windows mantém os argumentos originais em milissegundos. Inclui também o ajuste do teste de propagação de exceções (#625).
Validação já realizada nos PRs: sockets IPv4/IPv6, HTTP real em Console/Daemon Linux e Console/VCL Windows, Indy antigo e moderno, suíte Delphi 13 com 335 testes aprovados em Tree e 335 em Radix. CI do master aprovado após ambos os merges. A release repete testes relevantes de keep-alive; os resultados serão registrados nas notas.
Conforme o checklist, a tag e a release serão publicadas após integrar este PR. O lockfile dos testes será regenerado pelo Boss em um PR separado, depois da publicação.