[PR #797] [MERGED] build(deps): bump tracing-error from 0.2.0 to 0.2.1 #7977

Closed
opened 2026-05-23 02:56:19 +01:00 by JakeStanger · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/JakeStanger/ironbar/pull/797
Author: @dependabot[bot]
Created: 12/2/2024
Status: Merged
Merged: 12/4/2024
Merged by: @JakeStanger

Base: masterHead: dependabot/cargo/tracing-error-0.2.1


📝 Commits (1)

  • 2338f29 build(deps): bump tracing-error from 0.2.0 to 0.2.1

📊 Changes

2 files changed (+3 additions, -3 deletions)

View changed files

📝 Cargo.lock (+2 -2)
📝 Cargo.toml (+1 -1)

📄 Description

Bumps tracing-error from 0.2.0 to 0.2.1.

Release notes

Sourced from tracing-error's releases.

tracing-error 0.2.1

[ [crates.io][crate-0.2.1] ] | [ [docs.rs][docs-0.2.1] ]

Changed

  • Bump MSRV to 1.63 (#2793)

Documented

  • Use intra-doc links instead of relative file paths (#2068)
  • More intra-doc links (#2077)
  • Add missing backtick to prelude docs (#2120)

#2068: tokio-rs/tracing#2068 #2077: tokio-rs/tracing#2077 #2120: tokio-rs/tracing#2120 #2793: tokio-rs/tracing#2793 [docs-0.2.1]: https://docs.rs/tracing-error/0.2.1/tracing_error/ [crate-0.2.1]: https://crates.io/crates/tracing-error/0.2.1

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/JakeStanger/ironbar/pull/797 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 12/2/2024 **Status:** ✅ Merged **Merged:** 12/4/2024 **Merged by:** [@JakeStanger](https://github.com/JakeStanger) **Base:** `master` ← **Head:** `dependabot/cargo/tracing-error-0.2.1` --- ### 📝 Commits (1) - [`2338f29`](https://github.com/JakeStanger/ironbar/commit/2338f2994042ca543f30a3e029d8b36de7369132) build(deps): bump tracing-error from 0.2.0 to 0.2.1 ### 📊 Changes **2 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+2 -2) 📝 `Cargo.toml` (+1 -1) </details> ### 📄 Description Bumps [tracing-error](https://github.com/tokio-rs/tracing) from 0.2.0 to 0.2.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tokio-rs/tracing/releases">tracing-error's releases</a>.</em></p> <blockquote> <h2>tracing-error 0.2.1</h2> <p>[ [crates.io][crate-0.2.1] ] | [ [docs.rs][docs-0.2.1] ]</p> <h3>Changed</h3> <ul> <li>Bump MSRV to 1.63 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/2793">#2793</a>)</li> </ul> <h3>Documented</h3> <ul> <li>Use intra-doc links instead of relative file paths (<a href="https://redirect.github.com/tokio-rs/tracing/issues/2068">#2068</a>)</li> <li>More intra-doc links (<a href="https://redirect.github.com/tokio-rs/tracing/issues/2077">#2077</a>)</li> <li>Add missing backtick to <code>prelude</code> docs (<a href="https://redirect.github.com/tokio-rs/tracing/issues/2120">#2120</a>)</li> </ul> <p><a href="https://redirect.github.com/tokio-rs/tracing/issues/2068">#2068</a>: <a href="https://redirect.github.com/tokio-rs/tracing/pull/2068">tokio-rs/tracing#2068</a> <a href="https://redirect.github.com/tokio-rs/tracing/issues/2077">#2077</a>: <a href="https://redirect.github.com/tokio-rs/tracing/pull/2077">tokio-rs/tracing#2077</a> <a href="https://redirect.github.com/tokio-rs/tracing/issues/2120">#2120</a>: <a href="https://redirect.github.com/tokio-rs/tracing/pull/2120">tokio-rs/tracing#2120</a> <a href="https://redirect.github.com/tokio-rs/tracing/issues/2793">#2793</a>: <a href="https://redirect.github.com/tokio-rs/tracing/pull/2793">tokio-rs/tracing#2793</a> [docs-0.2.1]: <a href="https://docs.rs/tracing-error/0.2.1/tracing_error/">https://docs.rs/tracing-error/0.2.1/tracing_error/</a> [crate-0.2.1]: <a href="https://crates.io/crates/tracing-error/0.2.1">https://crates.io/crates/tracing-error/0.2.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tokio-rs/tracing/commit/11487a00031c9e1b8497faca2683715c6e1729c8"><code>11487a0</code></a> chore: prepare tracing-error 0.2.1 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3163">#3163</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/311c31321657ba657ccf63e10bc92a45a079fa2b"><code>311c313</code></a> chore: prepare tracing-subscriber 0.3.19 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3162">#3162</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/35f360a1924319c822f20da412be66854bf9428b"><code>35f360a</code></a> chore: fix new Clippy lints in Rust 1.83.0 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3165">#3165</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/c66a692e671903712c1bd598082fc018f7f8568e"><code>c66a692</code></a> chore: prepare tracing-serde 0.2.0 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3160">#3160</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/0ca78870815a34a345a908f48db057057e8803d2"><code>0ca7887</code></a> chore: prepare tracing 0.1.41 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3159">#3159</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/504a287abbf93ef0ffae09688210f423e8061160"><code>504a287</code></a> tracing: update core to v0.1.33 and attributes to v0.1.28 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3156">#3156</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/baa54894067b245bad0af8e45f92279e25820659"><code>baa5489</code></a> chore: prepare tracing-attributes 0.1.28 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3155">#3155</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/cb0f0e71dd1020d63f2190ffef298b989c9e88b0"><code>cb0f0e7</code></a> chore: prepare tracing-core 0.1.33 (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3153">#3153</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/11c82730359f60b290cba0a405947b23c0a68d7b"><code>11c8273</code></a> subscriber: don't gate <code>with_ansi()</code> on the &quot;ansi&quot; feature (<a href="https://redirect.github.com/tokio-rs/tracing/issues/3020">#3020</a>)</li> <li><a href="https://github.com/tokio-rs/tracing/commit/8a25a16873d2970a6ac0577a0ceea916f3013424"><code>8a25a16</code></a> core: fix missed <code>register_callsite</code> error (<a href="https://redirect.github.com/tokio-rs/tracing/issues/2938">#2938</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tokio-rs/tracing/compare/tracing-error-0.2.0...tracing-error-0.2.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tracing-error&package-manager=cargo&previous-version=0.2.0&new-version=0.2.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
JakeStanger 2026-05-23 02:56:19 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
JakeStanger/ironbar#7977
No description provided.