Skip to content
This repository was archived by the owner on Oct 1, 2025. It is now read-only.

fix(deps): update dependency react-native-safe-area-context to v3.4.1#112

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-native-safe-area-context-3.x
Open

fix(deps): update dependency react-native-safe-area-context to v3.4.1#112
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/react-native-safe-area-context-3.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Aug 6, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-native-safe-area-context 3.2.0 -> 3.4.1 age adoption passing confidence

Release Notes

th3rdwave/react-native-safe-area-context

v3.4.1

Compare Source

  • Revert "Drop support for ios < 11". This will be done in v4 instead.

v3.4.0

Compare Source

  • Fix app extension build (d5fab0b)
  • Drop support for ios < 11

v3.3.2

Compare Source

  • Fix ReferenceError: React is not defined (#​212) in jest mock

v3.3.1

Compare Source

  • Use mavenCentral() since jcenter is shutting down (#​211)

v3.3.0

Compare Source


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 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.

@codecov
Copy link
Copy Markdown

codecov Bot commented Aug 6, 2021

Codecov Report

Merging #112 (adc558f) into master (1aabe4d) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #112   +/-   ##
=======================================
  Coverage   99.84%   99.84%           
=======================================
  Files          19       19           
  Lines         627      627           
  Branches       62       62           
=======================================
  Hits          626      626           
  Misses          1        1           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1aabe4d...adc558f. Read the comment docs.

@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from 769a08c to c28ae43 Compare August 31, 2021 16:45
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.3.0 fix(deps): update dependency react-native-safe-area-context to v3.3.1 Aug 31, 2021
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.3.1 fix(deps): update dependency react-native-safe-area-context to v3.3.2 Sep 1, 2021
@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from c28ae43 to 1c0d85f Compare September 1, 2021 19:07
@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from 1c0d85f to adc558f Compare March 7, 2022 13:07
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.3.2 fix(deps): update dependency react-native-safe-area-context to v3.4.1 Mar 7, 2022
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant