Skip to content

build(deps): bump chrono from 0.4.43 to 0.4.44#107

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/chrono-0.4.44
Closed

build(deps): bump chrono from 0.4.43 to 0.4.44#107
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/chrono-0.4.44

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Mar 2, 2026

Copy link
Copy Markdown
Contributor

Bumps chrono from 0.4.43 to 0.4.44.

Release notes

Sourced from chrono's releases.

0.4.44

What's Changed

Commits
  • c14b459 Bump version to 0.4.44
  • ea832c5 Add track_caller to non-deprecated functions
  • cfae889 Fix panic message in to_rfc2822
  • f8900b5 docs: match MSRV with Cargo.toml contents
  • See full diff 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 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)

Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.43 to 0.4.44.
- [Release notes](https://github.com/chronotope/chrono/releases)
- [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md)
- [Commits](chronotope/chrono@v0.4.43...v0.4.44)

---
updated-dependencies:
- dependency-name: chrono
  dependency-version: 0.4.44
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Mar 2, 2026
@benjamin-747 benjamin-747 marked this pull request as draft March 3, 2026 02:08
@genedna genedna marked this pull request as ready for review March 5, 2026 13:14
Copilot AI review requested due to automatic review settings March 5, 2026 13:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Dependabot patch-version bump of the chrono crate from 0.4.43 to 0.4.44. The upstream release adds track_caller to non-deprecated functions and a documentation fix — no breaking changes.

Changes:

  • Bump chrono version in Cargo.toml from 0.4.43 to 0.4.44
  • Update Cargo.lock with the new version and checksum

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
Cargo.toml Updated chrono dependency version from 0.4.43 to 0.4.44
Cargo.lock Updated lockfile with new chrono version and checksum

@dependabot @github

dependabot Bot commented on behalf of github Mar 5, 2026

Copy link
Copy Markdown
Contributor Author

Looks like chrono is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Mar 5, 2026
@dependabot dependabot Bot deleted the dependabot/cargo/chrono-0.4.44 branch March 5, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant