Skip to content

Update expo monorepo #121

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

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

Update expo monorepo #121

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
expo (source) 48.0.0 -> 48.0.9 age adoption passing confidence
expo-media-library (source) 15.2.2 -> 15.2.3 age adoption passing confidence
jest-expo (source) 46.0.1 -> 46.0.2 age adoption passing confidence

Release Notes

expo/expo (expo)

v48.0.9

Compare Source

v48.0.8

Compare Source

v48.0.7

Compare Source

v48.0.6

Compare Source

v48.0.5

Compare Source

v48.0.4

Compare Source

v48.0.3

Compare Source

v48.0.2

Compare Source

v48.0.1

Compare Source

This version does not introduce any user-facing changes.

expo/expo (expo-media-library)

v15.2.3

Compare Source

expo/expo (jest-expo)

v46.0.2

Compare Source

🐛 Bug fixes
⚠️ Notices

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 renovate bot force-pushed the renovate/expo-monorepo branch from d836bf5 to dcd227e Compare February 14, 2022 13:19
@renovate renovate bot force-pushed the renovate/expo-monorepo branch from dcd227e to 4adc76a Compare May 6, 2022 00:29
@renovate renovate bot force-pushed the renovate/expo-monorepo branch 3 times, most recently from b9f2d4d to c3d1897 Compare September 1, 2022 21:47
@renovate renovate bot force-pushed the renovate/expo-monorepo branch 2 times, most recently from e296cb0 to 6f827bb Compare October 2, 2022 22:02
@renovate renovate bot force-pushed the renovate/expo-monorepo branch from 6f827bb to c3430bb Compare October 6, 2022 09:41
@renovate renovate bot force-pushed the renovate/expo-monorepo branch from c3430bb to ec0d8d9 Compare October 13, 2022 21:39
@renovate renovate bot force-pushed the renovate/expo-monorepo branch 2 times, most recently from 6776914 to ab3f637 Compare November 9, 2022 08:28
@renovate renovate bot force-pushed the renovate/expo-monorepo branch from ab3f637 to 089b89f Compare March 14, 2023 15:30
@renovate renovate bot changed the title Update expo monorepo Update dependency jest-expo to v46.0.2 Mar 14, 2023
@renovate renovate bot changed the title Update dependency jest-expo to v46.0.2 Update expo monorepo Mar 15, 2023
@renovate renovate bot force-pushed the renovate/expo-monorepo branch 5 times, most recently from a622ea1 to 7747d43 Compare March 20, 2023 22:09
@renovate renovate bot force-pushed the renovate/expo-monorepo branch from 7747d43 to 4510258 Compare March 21, 2023 18:23
@renovate
Copy link
Author

renovate bot commented Mar 25, 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: package-lock.json
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants