elixir-google-api icon indicating copy to clipboard operation
elixir-google-api copied to clipboard

chore(deps): update dependency poison to v5

Open renovate-bot opened this issue 4 years ago • 2 comments

Mend Renovate

This PR contains the following updates:

Package Update Change
poison major ~> 3.1 -> ~> 5.0
poison major >= 3.0.0 and < 5.0.0 -> < 6.0.0

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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.

renovate-bot avatar Jul 22 '21 12:07 renovate-bot

⚠ 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: mix.lock
Command failed: docker run --rm --name=renovate_elixir --label=renovate_child -v "/mnt/renovate/gh/googleapis/elixir-google-api":"/mnt/renovate/gh/googleapis/elixir-google-api" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -w "/mnt/renovate/gh/googleapis/elixir-google-api" docker.io/renovate/elixir bash -l -c "mix deps.update poison"
warning: use Mix.Config is deprecated. Use the Config module instead
  config/config.exs:3

** (Mix) Hex dependency resolution failed, change the version requirements of your dependencies or unlock them (by using mix deps.update or mix deps.unlock). If you are unable to resolve the conflicts you can try overriding with {:dependency, "~> 1.0", override: true}

forking-renovate[bot] avatar Jul 22 '21 12:07 forking-renovate[bot]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot https://conventionalcommits.org/