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 dependency @4c/cli to v4 #80

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 27, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@4c/cli (source) ^3.0.1 -> ^4.0.4 age adoption passing confidence

Release Notes

4Catalyzer/cli (@​4c/cli)

v4.0.4

Compare Source

Note: Version bump only for package @​4c/cli

v4.0.3

Compare Source

Note: Version bump only for package @​4c/cli

v4.0.2

Compare Source

Note: Version bump only for package @​4c/cli

v4.0.1

Compare Source

Note: Version bump only for package @​4c/cli

v4.0.0

Compare Source

Features
BREAKING CHANGES
  • SVGO upgraded to v2, which requires a compatible config file

3.0.1 (2021-10-07)

Note: Version bump only for package @​4c/cli


Configuration

📅 Schedule: Branch creation - "before 4am" (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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovatebot label Mar 27, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Mar 27, 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: yarn.lock
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

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

Successfully merging this pull request may close these issues.

0 participants