docs: document 0.5.0 changes; bump version to 0.5.0 - #329
Merged
Merged
Conversation
Cut the 0.5.0 release: promote [Unreleased] to [0.5.0] and fill in the changes that landed since v0.4.0 without a changelog entry. - CHANGELOG: add the HTTP/2 write scheduler + RFC 9218 prioritization (res.setPriority), runtime OCSP staple rotation via reloadTls, the h3 rapid-reset budget, the new conformance/bench/chaos suites; the behavioural changes (case-sensitive h1 methods, framing/hop-by-hop header filtering, h1 linger close, EVP-backed HMAC/SHA-1, sendFile chunking/buffering); the h1/h2/h3 correctness-review fixes, flow-control leaks, keep-alive deadline, sendFile small-window deadlock, async-upload read-ahead bound, shutdown orphaned-future and pin-accounting fixes; and a Security summary. Fix the stale compare links (Unreleased pointed at v0.3.0; 0.4.0 had none). - README: document maxBlockingQueue / PoolSaturatedError / shutdownHardTimeout in the blocking section, writeTimeout in the config example, and res.setPriority in the Response API table. - HARDENING: add maxBlockingQueue, writeTimeout, shutdownHardTimeout rows; maxResetStreams now covers HTTP/3. - THREAT_MODEL: rapid reset covers HTTP/3, the slowloris row covers slow readers (writeTimeout) and the h2 head/body + zero-window deadlines, and a worker-pool saturation row. - vortex.nimble: 0.4.0 -> 0.5.0.
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
1 participant
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.
Cut the 0.5.0 release: promote
[Unreleased]to[0.5.0]and fill in the changes that landed since v0.4.0 without a changelog entry.res.setPriority), runtime OCSP staple rotation viareloadTls, the h3 rapid-reset budget, the new conformance/bench/chaos suites; the behavioural changes (case-sensitive h1 methods, framing/hop-by-hop header filtering, h1 linger close, EVP-backed HMAC/SHA-1, sendFile chunking/buffering); the h1/h2/h3 correctness-review fixes, flow-control leaks, keep-alive deadline, sendFile small-window deadlock, async-upload read-ahead bound, shutdown orphaned-future and pin-accounting fixes; and a Security summary. Fix the stale compare links (Unreleased pointed at v0.3.0; 0.4.0 had none).maxBlockingQueue/PoolSaturatedError/shutdownHardTimeoutin the blocking section,writeTimeoutin the config example, andres.setPriorityin the Response API table.maxBlockingQueue,writeTimeout,shutdownHardTimeoutrows;maxResetStreamsnow covers HTTP/3.writeTimeout) and the h2 head/body + zero-window deadlines, and a worker-pool saturation row.Docs and version only; no code change. After merge: tag
v0.5.0and publish the GitHub release with the 0.5.0 changelog section as the body.