Bump tokio from 1.48.0 to 1.49.0#306
Merged
Merged
Conversation
Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.48.0 to 1.49.0. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-1.48.0...tokio-1.49.0) --- updated-dependencies: - dependency-name: tokio dependency-version: 1.49.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
aram356
approved these changes
Feb 13, 2026
aram356
added a commit
that referenced
this pull request
Jul 3, 2026
Switch the six edgezero git deps from branch main to worktree-state-nested-secrets-spec-review (stackpop/edgezero#306, stacked on #300) to pick up the Phase 0 State<T> extractor work. cargo check-axum passes.
aram356
added a commit
that referenced
this pull request
Jul 3, 2026
The prior review's Critical 'APIs do not exist' findings were against a stale cargo-cache checkout (ce6bcf7, edgezero #253 'Add store support for Spin') that predates the registry refactor. Our actual pin is 6ebc29a5 (PR #306), which HAS StoreRegistry/StoresMetadata/Hooks::stores()/dispatch_with_registries/ with_*_registry/[stores.*] ids+default/CF-KV-namespace/Axum-local-file. Added a 'Pinned dependency (verified)' note recording this to prevent re-litigation. Valid fixes: - Cloudflare app.rs settings_from_cloudflare_config_json reads literal value.get("app_config") from the side-channel; change to CONFIG_BLOB_KEY so the key rename doesn't break Cloudflare boot (Phase 2 does the store migration) - Viceroy generator already emits a trusted_server_config store for rollout flags; the app_config->trusted_server_config rename must MERGE the blob into that table, not emit a duplicate table
aram356
added a commit
that referenced
this pull request
Jul 4, 2026
aram356
added a commit
that referenced
this pull request
Jul 5, 2026
…Meta P0 (State<T> + nested/array #[secret]) landed on the #306 branch. The nested-secret work reshapes AppConfigMeta: const SECRET_FIELDS -> fn secret_fields() -> Vec<SecretField>. Update TrustedServerAppConfig's impl accordingly (still empty until Phase 3 secret externalization). Verified: cargo check green on core + all four adapters + cli.
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps tokio from 1.48.0 to 1.49.0.
Release notes
Sourced from tokio's releases.
... (truncated)
Commits
e3b89bbchore: prepare Tokio v1.49.0 (#7824)4f577b8Merge 'tokio-1.47.3' into 'master'f320197chore: prepare Tokio v1.47.3 (#7823)ea6b144ci: freeze rustc on nightly-2025-01-25 innetlify.toml(#7652)264e703Mergetokio-1.43.4intotokio-1.47.x(#7822)dfb0f00chore: prepare Tokio v1.43.4 (#7821)4a91f19ci: fix wasm32-wasip1 tests (#7788)601c383ci: upgrade FreeBSD from 14.2 to 14.3 (#7758)484cb52sync: returnTryRecvError::DisconnectedfromReceiver::try_recvafter `Re...16f20c3rt: mentionLocalRuntimeinnew_current_threaddocs (#7820)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)