Skip to content
This repository was archived by the owner on Aug 6, 2023. It is now read-only.

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

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#46
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 Nov 4, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-native-safe-area-context 3.1.7 -> 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

v3.2.0

Compare Source

Minor bugfixes and improvements

  • set displayName in contexts (#​166)
  • Update Android Tools gradle version (#​173)
  • Fix for when not using autolinking (#​169)
  • Fix crash on ios10 (#​180)
  • If view extends beyond window boundaries, do not add that difference to the insets (#​177)
  • Fix crash if content view is null on Android (81d40a8)

v3.1.9

Compare Source

  • [Infrastructure] Reduce npm package size (#​157)

v3.1.8

Compare Source

  • fix: autolinking when using Xcode 12 (#​147)

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.

@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from 626a29c to 4aa1e70 Compare November 11, 2020 20:44
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.1.8 fix(deps): update dependency react-native-safe-area-context to v3.1.9 Nov 11, 2020
@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from 4aa1e70 to e06e7a9 Compare March 7, 2021 20:41
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.1.9 fix(deps): update dependency react-native-safe-area-context to v3.2.0 Mar 7, 2021
@renovate renovate Bot changed the title fix(deps): update dependency react-native-safe-area-context to v3.2.0 fix(deps): update dependency react-native-safe-area-context to v3.3.2 Oct 18, 2021
@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from e06e7a9 to c196d89 Compare October 18, 2021 23:21
@renovate renovate Bot force-pushed the renovate/react-native-safe-area-context-3.x branch from c196d89 to dc7cd8f Compare March 7, 2022 09:24
@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 23, 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