Repository navigation
chore(deps): update rust crate tower-http to v0.7.1 - #553
Merged
Merged
Conversation
|
PR author is in the excluded authors list. |
renovate
Bot
force-pushed
the
renovate/alien-370-tower-http-0.x-lockfile
branch
2 times, most recently
from
September 7, 2026 21:05
f06012c to
2961ece
Compare
renovate
Bot
force-pushed
the
renovate/alien-370-tower-http-0.x-lockfile
branch
from
September 15, 2026 08:55
2961ece to
d667fcf
Compare
renovate
Bot
force-pushed
the
renovate/alien-370-tower-http-0.x-lockfile
branch
from
September 24, 2026 12:28
d667fcf to
bfa3248
Compare
alongubkin
added a commit
that referenced
this pull request
Oct 5, 2026
…'s changelog (#876) ## What Two release-flow bugs that would hit the next stable release: 1. **The next version PR fails "Release qualification".** Prepare now bumps `infra/helm/alien-manager/Chart.yaml` and `infra/aws-ecs-manager/variables.tf`, but the detect step's file allowlist in `release-qualification.yml` doesn't list them, so it fails with "Release PR contains non-version files". 2. **Each GitHub release body lists the previous release's changes.** `generate-changelog` runs `git-cliff --latest` before the new tag exists, so it renders the range ending at the previous tag. The v3.3.26 body lists #707–#756, which shipped in v3.3.25. ## How 1. Add both files to the allowlist, and normalize their version fields (`version`/`appVersion` in the chart, the `alien-manager:v…` image default in the module) so any other change to them still fails the check. 2. Use `--unreleased --tag v<version>`: the commits since the last tag, rendered under the new version. ## Verification - On a scratch commit that applies prepare's own `sed` bumps for 3.3.27 to `main`: the old allowlist rejects exactly the two files; the new allowlist and the metadata check pass. A second scratch commit that also changes `type:` in the chart and the image registry in the module fails with "Release PR changes non-version metadata". - `git-cliff 2.14.2` with `cliff.toml` on `main`: `--latest` renders #753–#779 (the v3.3.26 range); `--unreleased --tag v3.3.27` renders #553–#873, the 68 commits since v3.3.26. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
This PR contains the following updates:
0.7.0→0.7.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
tower-rs/tower-http (tower-http)
v0.7.1Compare Source
Added
fs: addServeDir::redirect_to_trailing_slash()to serve directory indexes directly instead of first redirecting to the trailing-slash path. The redirect remains the default (#728)fs: addignore_multi_range_requests()toServeDirandServeFile, serving the full representation when a request asks for multiple byte ranges. The existing416 Range Not Satisfiableresponse remains the default (#727)request-id: the constructors and accessors on the request-id layers, services, andRequestIdare nowconst fn, so they can be used in const context (#716)Changed
fs: the minimumhttp-range-headerrequirement is now 0.4.2 (#661)Fixed
fs: makeServeDir::try_callpropagate expected filesystemI/O errors when no fallback is configured, as documented, instead of converting
them to
404 Not Foundresponses (#718)decompression: don't end the body when a data frame with no remaining bytesarrives after the decompressor reports end-of-stream. Trailers following such a
frame were dropped and could not be recovered (#722)
decompression: return a body error when a data frame with remaining bytesarrives after the decompressor reports end-of-stream, rather than silently
truncating. This regressed in 0.7.0 (#712)
fs: multipart range requests are now rejected before range validation, sothey consistently return
416 Range Not Satisfiablewith aCannot serve multipart range requestsbody instead of a genericunsatisfiable-range response (#661)
fs: range error responses no longer carry representation headers such asContent-TypeandContent-Encoding(#727)set-header:SetMultipleResponseHeadersLayerandSetMultipleResponseHeaderare now
Cloneregardless of the response body type, matching the fix appliedto the request-side types in 0.7.0 (#714)
All the changes
New Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.