chore(deps): bump tower-http from 0.6.11 to 0.7.0 - #524
Merged
Conversation
Bumps [tower-http](https://github.com/tower-rs/tower-http) from 0.6.11 to 0.7.0. - [Release notes](https://github.com/tower-rs/tower-http/releases) - [Commits](tower-rs/tower-http@tower-http-0.6.11...tower-http-0.7.0) --- updated-dependencies: - dependency-name: tower-http dependency-version: 0.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Checkpoint of work in progress, touching Cargo.toml. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
Adds end-to-end tests for the board columns feature, covering the creation, renaming, and deletion of columns to ensure the core workflow is protected against regressions. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
Updated the tower-http dependency in Cargo.lock to include an explicit version specifier, ensuring consistent resolution of the dependency across builds. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
There was a problem hiding this comment.
tinysweeper found nothing blocking. Approving.
$0.0007 · 10,755 in / 2,221 out · 9,362 cached (87%) · z-ai/glm-5.2
critique: $0.0003 · 2,849 in / 873 out · 2,409 cached (85%) · z-ai/glm-5.2
security: $0.0002 · 3,312 in / 477 out · 2,865 cached (87%) · z-ai/glm-5.2
description: $0.0003 · 4,594 in / 871 out · 4,088 cached (89%) · z-ai/glm-5.2
There was a problem hiding this comment.
tinysweeper found nothing blocking. Approving.
$0.0013 · 11,591 in / 4,943 out · 9,945 cached (86%) · z-ai/glm-5.2
critique: $0.0008 · 3,148 in / 3,106 out · 2,543 cached (81%) · z-ai/glm-5.2
security: $0.0003 · 3,670 in / 894 out · 3,155 cached (86%) · z-ai/glm-5.2
description: $0.0003 · 4,773 in / 943 out · 4,247 cached (89%) · z-ai/glm-5.2
Adds end-to-end tests for the board columns feature, covering the creation, renaming, and deletion of columns to ensure the core workflow functions correctly in a real browser environment. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
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.
Bumps tower-http from 0.6.11 to 0.7.0.
Summary
Dependency bump only:
tower-http = { version = "0.7", features = ["fs"] }, consumed viaServeDir/ServeFile(the axum SPA fallback). No code changes were required for the 0.7 API —the
fsfeature used here is unchanged.Two small follow-up commits were needed to keep the repository's own gates green after the bump:
Cargo.locksync (8b2bf54) — the bump introducedtower-http 0.7.0into the lock alongside theretained
0.6.11(pulled in transitively byreqwest 0.13.4, which requires^0.6.8). Cargorequires dependency references to be version-qualified once two versions coexist in the lock;
the
reqwestentry still read baretower-http, socargo metadata --locked(the CI"Verify Cargo.lock is in sync" step) failed after the upstream/main merge. Regenerated the lock
with
cargo metadata; the resulting one-line change qualifies the reference astower-http 0.6.11.frontend/test/e2e/board-columns.spec.tsrace fix (d396222) — the "a card dropped intoPlanning is planned and settled, never left parked" test (live-brain lane only) polls
.not.toBe("planning")immediately after the drop, which could pass on the seed column(
todo) before the move reached the host, and then assert a card still mid-planning-pass.It now waits for the transition into
planningfirst — the same first step the mock-lanetest takes — and then waits for the pass to settle it. This was a flaky test (the same commit
passed on a sibling CI run), not a product regression.
Commands run locally
Behavior changes
None to the product. The e2e test above is made deterministic; the console and board behavior it
asserts is unchanged.