[PR #180] [MERGED] build(deps): bump chrono from 0.4.25 to 0.4.26 #7559

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

📋 Pull Request Information

Original PR: https://github.com/JakeStanger/ironbar/pull/180
Author: @dependabot[bot]
Created: 6/5/2023
Status: Merged
Merged: 6/5/2023
Merged by: @JakeStanger

Base: masterHead: dependabot/cargo/chrono-0.4.26


📝 Commits (1)

  • f37bc80 build(deps): bump chrono from 0.4.25 to 0.4.26

📊 Changes

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

View changed files

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

📄 Description

Bumps chrono from 0.4.25 to 0.4.26.

Release notes

Sourced from chrono's releases.

0.4.26

The changes from #807 we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in #1113. A small amount of other changes were merged since.

Thanks on behalf of the chrono team (@​djc and @​esheppa) to all contributors!

Commits
  • 5b8449e Bump version to 0.4.26
  • 7e6646d Update README
  • 8bd13db Use result in doctest
  • becc222 Revert backport of #807
  • 373c6e4 Update to 2021 edition
  • e41451d try_verify_against_date_command NFC print progress messages
  • b1729f3 try_verify_against_date sanity check date command
  • 05c9408 consolidate path to date
  • b5b936a Error on negative durations in DurationRound
  • c0d848d parse tests around nanosecond parsing bare '.'
  • Additional commits viewable in compare view

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 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/180 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/5/2023 **Status:** ✅ Merged **Merged:** 6/5/2023 **Merged by:** [@JakeStanger](https://github.com/JakeStanger) **Base:** `master` ← **Head:** `dependabot/cargo/chrono-0.4.26` --- ### 📝 Commits (1) - [`f37bc80`](https://github.com/JakeStanger/ironbar/commit/f37bc8029276c9abfbfd8a85a90083e4d2bc8343) build(deps): bump chrono from 0.4.25 to 0.4.26 ### 📊 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 [chrono](https://github.com/chronotope/chrono) from 0.4.25 to 0.4.26. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/chronotope/chrono/releases">chrono's releases</a>.</em></p> <blockquote> <h2>0.4.26</h2> <p>The changes from <a href="https://redirect.github.com/chronotope/chrono/issues/807">#807</a> we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in <a href="https://redirect.github.com/chronotope/chrono/issues/1113">#1113</a>. A small amount of other changes were merged since.</p> <ul> <li>Update README (<a href="https://redirect.github.com/chronotope/chrono/issues/1111">#1111</a>, thanks to <a href="https://github.com/pitdicker"><code>@​pitdicker</code></a>)</li> <li>Revert backport of <a href="https://redirect.github.com/chronotope/chrono/issues/807">#807</a> (<a href="https://redirect.github.com/chronotope/chrono/issues/1113">#1113</a>, thanks to <a href="https://github.com/pitdicker"><code>@​pitdicker</code></a>)</li> <li>Update to 2021 edition (<a href="https://redirect.github.com/chronotope/chrono/issues/1109">#1109</a>, thanks to <a href="https://github.com/tottoto"><code>@​tottoto</code></a>)</li> <li>Fix <code>DurationRound</code> panics from issue <a href="https://redirect.github.com/chronotope/chrono/issues/1010">#1010</a> (<a href="https://redirect.github.com/chronotope/chrono/issues/1093">#1093</a>, thanks to <a href="https://github.com/pitdicker"><code>@​pitdicker</code></a>)</li> <li>tests: date path consolidate (branch 0.4.x) (<a href="https://redirect.github.com/chronotope/chrono/issues/1090">#1090</a>, thanks to <a href="https://github.com/jtmoon79"><code>@​jtmoon79</code></a>)</li> <li>Parse tests nanosecond bare dot (branch 0.4.x) (<a href="https://redirect.github.com/chronotope/chrono/issues/1098">#1098</a>, thanks to <a href="https://github.com/jtmoon79"><code>@​jtmoon79</code></a>)</li> <li>yamllint cleanup lint.yml test.yml (<a href="https://redirect.github.com/chronotope/chrono/issues/1102">#1102</a>, thanks to <a href="https://github.com/jtmoon79"><code>@​jtmoon79</code></a>)</li> <li>Remove num-iter dependency (<a href="https://redirect.github.com/chronotope/chrono/issues/1107">#1107</a>, thanks to <a href="https://github.com/tottoto"><code>@​tottoto</code></a>)</li> </ul> <p>Thanks on behalf of the chrono team (<a href="https://github.com/djc"><code>@​djc</code></a> and <a href="https://github.com/esheppa"><code>@​esheppa</code></a>) to all contributors!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/chronotope/chrono/commit/5b8449e1f2fb863c2a2c69368a5c5e0366821fc8"><code>5b8449e</code></a> Bump version to 0.4.26</li> <li><a href="https://github.com/chronotope/chrono/commit/7e6646d85b1e1f511d2ab9436e48bd113aa78b36"><code>7e6646d</code></a> Update README</li> <li><a href="https://github.com/chronotope/chrono/commit/8bd13db2425301a9b60a309a79b61c72f1cf79f0"><code>8bd13db</code></a> Use result in doctest</li> <li><a href="https://github.com/chronotope/chrono/commit/becc22219d12f7fd27b2811618e9d432baf4acc5"><code>becc222</code></a> Revert backport of <a href="https://redirect.github.com/chronotope/chrono/issues/807">#807</a></li> <li><a href="https://github.com/chronotope/chrono/commit/373c6e46de5f412e3c19c541d53b719f8a50b185"><code>373c6e4</code></a> Update to 2021 edition</li> <li><a href="https://github.com/chronotope/chrono/commit/e41451dedc2d5d5b07f9582689bbbd7d91b3233f"><code>e41451d</code></a> try_verify_against_date_command NFC print progress messages</li> <li><a href="https://github.com/chronotope/chrono/commit/b1729f3a9b17e242509329d202d9923926bc814d"><code>b1729f3</code></a> try_verify_against_date sanity check date command</li> <li><a href="https://github.com/chronotope/chrono/commit/05c9408f434906851730c0698a19cad847107aa0"><code>05c9408</code></a> consolidate path to <code>date</code></li> <li><a href="https://github.com/chronotope/chrono/commit/b5b936af515f4cce124841bcd708d4591007bfa5"><code>b5b936a</code></a> Error on negative durations in <code>DurationRound</code></li> <li><a href="https://github.com/chronotope/chrono/commit/c0d848d4c815d8288d1387fade64ca9af50655b5"><code>c0d848d</code></a> parse tests around nanosecond parsing bare '.'</li> <li>Additional commits viewable in <a href="https://github.com/chronotope/chrono/compare/v0.4.25...v0.4.26">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=chrono&package-manager=cargo&previous-version=0.4.25&new-version=0.4.26)](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 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:55:10 +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#7559
No description provided.