Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate diesel-async to 0.5.0 #115

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2023

This PR contains the following updates:

Package Type Update Change
diesel-async dependencies minor 0.3.2 -> 0.5.0

Release Notes

weiznich/diesel_async (diesel-async)

v0.5.1

Compare Source

  • Add crate feature pool for extending connection pool implements through external crate
  • Implement Deref and DerefMut for AsyncConnectionWrapper to allow using it in an async context as well

v0.5.0

Compare Source

  • Added type diesel_async::pooled_connection::mobc::PooledConnection
  • MySQL/MariaDB now use CLIENT_FOUND_ROWS capability to allow consistent behaviour with PostgreSQL regarding return value of UPDATe commands.
  • The minimal supported rust version is now 1.78.0
  • Add a SyncConnectionWrapper type that turns a sync connection into an async one. This enables SQLite support for diesel-async
  • Add support for diesel::connection::Instrumentation to support logging and other instrumentation for any of the provided connection impls.
  • Bump minimal supported mysql_async version to 0.34

v0.4.1

Compare Source

  • Fixed feature flags for docs.rs

v0.4.0

Compare Source

  • Add a AsyncConnectionWrapper type to turn a diesel_async::AsyncConnection into a diesel::Connection. This might be used to execute migrations via diesel_migrations.
  • Add some connection pool configurations to specify how connections
    in the pool should be checked if they are still valid

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Sep 1, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: server/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path server/infra/db_repository_impl/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `sentry`.
    ... required by package `seichi-timed-stats-conifers-ingestor v0.1.0 (/tmp/renovate/repos/github/GiganticMinecraft/seichi-timed-stats-conifers/server/ingestor)`
versions that meet the requirements `^0.31.7` are: 0.31.8, 0.31.7

the package `seichi-timed-stats-conifers-ingestor` depends on `sentry`, with features: `profiling` but `sentry` does not have these features.


failed to select a version for `sentry` which could resolve this conflict

@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch from 6953d41 to bf67ca0 Compare September 1, 2023 12:57
@renovate renovate bot changed the title fix(deps): update rust crate diesel-async to 0.4.0 fix(deps): update rust crate diesel-async to 0.4.1 Sep 1, 2023
@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch 3 times, most recently from 6ef15bd to 30d6b9f Compare September 6, 2023 21:07
@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch 9 times, most recently from dd7e0ca to 9791736 Compare October 18, 2023 22:48
@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch 8 times, most recently from ee59f27 to 281b66d Compare April 17, 2024 15:11
@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch from 281b66d to 582d2c5 Compare May 5, 2024 10:53
@renovate renovate bot changed the title fix(deps): update rust crate diesel-async to 0.4.1 fix(deps): update rust crate diesel-async to 0.4.0 May 5, 2024
@renovate renovate bot force-pushed the renovate/diesel-async-0.x branch from 582d2c5 to 002e76f Compare July 19, 2024 14:38
@renovate renovate bot changed the title fix(deps): update rust crate diesel-async to 0.4.0 fix(deps): update rust crate diesel-async to 0.5.0 Jul 19, 2024
Copy link
Contributor Author

renovate bot commented Jul 19, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: server/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path server/infra/db_repository_impl/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `sentry`.
    ... required by package `seichi-timed-stats-conifers-ingestor v0.1.0 (/tmp/renovate/repos/github/GiganticMinecraft/seichi-timed-stats-conifers/server/ingestor)`
versions that meet the requirements `^0.31.7` are: 0.31.8, 0.31.7

the package `seichi-timed-stats-conifers-ingestor` depends on `sentry`, with features: `profiling` but `sentry` does not have these features.


failed to select a version for `sentry` which could resolve this conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants