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

chore(deps): update rust crate marine-rs-sdk-main to 0.12.0 - autoclosed #384

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
marine-rs-sdk-main (source) dependencies minor 0.10.0 -> 0.12.0

Release Notes

fluencelabs/marine-rs-sdk (marine-rs-sdk-main)

v0.12.0

⚠ BREAKING CHANGES
  • introduce host import API versions (#​154)
Features

v0.11.0

⚠ BREAKING CHANGES
  • ABI, call-parameters: add worker_id field into CallParameters (#​151)
Features
  • ABI, call-parameters: add worker_id field into CallParameters (#​151) (3bdf0c2)

v0.10.3

Features

v0.10.2

Bug Fixes
  • ABI: use correct empty string/vector representation (#​146) (d3cade9)

v0.10.1

Features

Configuration

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

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

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@github-actions
Copy link

Pull Request Test Coverage Report for Build 6675547954

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 0.418%

Totals Coverage Status
Change from base Build 6616846004: 0.0%
Covered Lines: 31
Relevant Lines: 7421

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from 3f1ab39 to 584b131 Compare November 7, 2023 13:51
@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from 584b131 to c90a5ac Compare December 12, 2023 19:09
@renovate renovate bot changed the title chore(deps): update rust crate marine-rs-sdk-main to 0.10.1 chore(deps): update rust crate marine-rs-sdk-main to 0.10.2 Dec 12, 2023
@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from c90a5ac to 27f7dc2 Compare December 14, 2023 12:15
@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from 27f7dc2 to 30193e4 Compare December 28, 2023 12:37
@renovate renovate bot changed the title chore(deps): update rust crate marine-rs-sdk-main to 0.10.2 chore(deps): update rust crate marine-rs-sdk-main to 0.10.3 Dec 28, 2023
@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from 30193e4 to 67e371a Compare January 9, 2024 17:33
@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch 3 times, most recently from 67704e7 to 9cedf16 Compare February 6, 2024 13:31
@renovate renovate bot changed the title chore(deps): update rust crate marine-rs-sdk-main to 0.10.3 chore(deps): update rust crate marine-rs-sdk-main to 0.11.0 Feb 6, 2024
Copy link
Contributor Author

renovate bot commented Feb 6, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path tools/repl/Cargo.toml --package [email protected] --precise 0.12.0
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 the requirement `marine-rs-sdk-main = "=0.10.0"`
candidate versions found which didn't match: 0.12.0
location searched: crates.io index
required by package `marine-rs-sdk v0.10.0`
    ... which satisfies dependency `marine-rs-sdk = "^0.10.0"` (locked to 0.10.0) of package `lilo-after-2gb-test v0.1.0 (/tmp/renovate/repos/github/fluencelabs/marine/core/tests/wasm_tests/lilo_after_2gb)`
perhaps a crate was updated and forgotten to be re-vendored?

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path marine/Cargo.toml --package [email protected] --precise 0.12.0
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 the requirement `marine-rs-sdk-main = "=0.10.0"`
candidate versions found which didn't match: 0.12.0
location searched: crates.io index
required by package `marine-rs-sdk v0.10.0`
    ... which satisfies dependency `marine-rs-sdk = "^0.10.0"` (locked to 0.10.0) of package `lilo-after-2gb-test v0.1.0 (/tmp/renovate/repos/github/fluencelabs/marine/core/tests/wasm_tests/lilo_after_2gb)`
perhaps a crate was updated and forgotten to be re-vendored?

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/module-info-parser/Cargo.toml --package [email protected] --precise 0.12.0
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 the requirement `marine-rs-sdk-main = "=0.10.0"`
candidate versions found which didn't match: 0.12.0
location searched: crates.io index
required by package `marine-rs-sdk v0.10.0`
    ... which satisfies dependency `marine-rs-sdk = "^0.10.0"` (locked to 0.10.0) of package `lilo-after-2gb-test v0.1.0 (/tmp/renovate/repos/github/fluencelabs/marine/core/tests/wasm_tests/lilo_after_2gb)`
perhaps a crate was updated and forgotten to be re-vendored?

@renovate renovate bot force-pushed the renovate/marine-rs-sdk-main-0.x branch from 9cedf16 to 0e4e8c7 Compare February 8, 2024 13:01
@renovate renovate bot changed the title chore(deps): update rust crate marine-rs-sdk-main to 0.11.0 chore(deps): update rust crate marine-rs-sdk-main to 0.12.0 Feb 8, 2024
@renovate renovate bot changed the title chore(deps): update rust crate marine-rs-sdk-main to 0.12.0 chore(deps): update rust crate marine-rs-sdk-main to 0.12.0 - autoclosed Feb 8, 2024
@renovate renovate bot closed this Feb 8, 2024
@renovate renovate bot deleted the renovate/marine-rs-sdk-main-0.x branch February 8, 2024 13:41
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