chore: bump tick to 0.7.0 and seatbelt to 0.9.0 - #193
Merged
Merged
Conversation
Bumps [tick](https://github.com/microsoft/oxidizer) from 0.6.0 to 0.7.0. - [Release notes](https://github.com/microsoft/oxidizer/releases) - [Changelog](https://github.com/microsoft/oxidizer/blob/main/CHANGELOG.md) - [Commits](microsoft/oxidizer@tick-v0.6.0...tick-v0.7.0) --- updated-dependencies: - dependency-name: tick dependency-version: 0.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Resolve the incompatible tick versions at the seatbelt boundary.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Bumps the workspace tick dependency from 0.6.0 to 0.7.0 and refreshes the lockfile.
Changes:
- Updates the workspace
tickdependency. - Adds the new transitive dependency resolutions.
- Leaves
seatbeltontick0.6.0, causing an incompatible clock boundary.
| File | Summary |
|---|---|
Cargo.toml |
Updates tick; requires aligning seatbelt or retaining tick 0.6.0 for this consumer. |
Cargo.lock |
Records tick 0.7.0 while retaining seatbelt’s tick 0.6.0 dependency. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
martinhavelka (wukchung)
enabled auto-merge (squash)
September 23, 2026 08:22
seatbelt 0.8.0 depends on tick 0.6.0, so bumping tick alone left two incompatible tick versions in the graph and broke compilation: cargo-aprz-lib passes a tick 0.7 Clock to seatbelt::ResilienceContext::new, which required AsRef<Clock> for tick 0.6. seatbelt 0.9.0 requires tick 0.7.0 and thread_aware 0.12.0, collapsing the duplicates back to a single version of each. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0aa90c03-7fa3-412a-8be8-4955f0e436cc
martinhavelka (wukchung)
changed the title
|
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (98.1%) is below the target coverage (100.0%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #193 +/- ##
=======================================
- Coverage 98.2% 98.1% -0.1%
=======================================
Files 307 309 +2
Lines 83775 85048 +1273
=======================================
+ Hits 82271 83503 +1232
- Misses 1504 1545 +41
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
martinhavelka (wukchung)
approved these changes
Sep 23, 2026
Evgenii (Vaiz)
approved these changes
Sep 23, 2026
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 tick from 0.6.0 to 0.7.0.
Release notes
Sourced from tick's releases.
Commits
5fd2577fix: use paths for workspace dev-dependencies (#758)84083b8refactor(benches): adopt metabench for routerama, multitude, internity, plura...9794095chore(release): prepare 58 coordinated crate releases (#739)369796efix(rallocator): keep stack-grouped allocations on a single call site (#748)704eba8fix(metabench_macros_impl): bound support identifier length via fixed-widh ha...03e3dfefeat(compressors): add streaming compression crate (#722)8624f90feat(seismograph): introduce runtime recording (#733)86b3b65feat: introduce metabench, a unified benchmarking framework (#732)bdafbc4fix(ci): let the nightly Miri job honour strict-provenance ignores (#664)efd8178feat(arty): introduce runtime facade and core crates (#727)@dependabot rebase. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---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)