pentarex / react-native-gallery-manager

30 stars 41 forks source link

Bump debug, react-native, babel-jest, babel-preset-react-native and jest in /example #37

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps debug to 4.3.4 and updates ancestor dependencies debug, react-native, babel-jest, babel-preset-react-native and jest. These dependencies need to be updated together.

Updates debug from 2.2.0 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

New Contributors

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.


Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits
  • da66c86 4.3.4
  • 9b33412 replace deprecated String.prototype.substr() (#876)
  • c0805cc add section about configuring JS console to show debug messages (#866)
  • 043d3cd 4.3.3
  • 4079aae update license and more maintainership information
  • 19b36c0 update repository location + maintainership information
  • f851b00 adds README section regarding usage in child procs (#850)
  • d177f2b Remove accidental epizeuxis
  • e47f96d 4.3.2
  • 1e9d38c cache enabled status per-logger (#799)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.


Updates react-native from 0.54.0 to 0.70.6

Release notes

Sourced from react-native's releases.

0.70.6

Fixed

  • Fixed regression: @​jest/create-cache-key-function dependency was inadvertedly bumped to 29.x. We are bringing it back to 27.0.1. (fb0e88beb9 by @​kelset)

Changed

iOS specific


You can participate in the conversation on the status of this release in this discussion


To help you upgrade to this version, you can use the upgrade helper ⚛️


You can find the whole changelog history in the changelog.md file.

0.70.5

Hotfix

This version is a patch release addressing the Android build issue that has been ongoing since Nov 4th 2022. If you are on 0.70.x, update to this version to fix it.

If you are on an older version of React Native, refer to this issue for details and the workaround you can apply in your project.


You can participate in the conversation on the status of this release in this discussion


To help you upgrade to this version, you can use the upgrade helper ⚛️


You can find the whole changelog history in the changelog.md file.

0.70.4

... (truncated)

Changelog

Sourced from react-native's changelog.

v0.70.6

Fixed

  • Fixed regression: @​jest/create-cache-key-function dependency was inadvertedly bumped to 29.x. We are bringing it back to 27.0.1. (fb0e88beb9 by @​kelset)

Changed

iOS specific

v0.70.5

Fixed

v0.70.4

Changed

Fixed

iOS specific

v0.70.3

Fixed

  • Stop styles from being reset when detaching Animated.Values in old renderer (2f58e52006 by @​javache)
  • Revert "Fix TextInput dropping text when used as uncontrolled component with defaultValue" to fix TextInputs not being settable to undefined programmatically (e2645a5) by Garrett Forbes Monroe

Android specific

iOS specific

... (truncated)

Commits
  • 49dd38f [0.70.6] Bump version numbers
  • fb0e88b [LOCAL] correct fix: bring back jest cache but on the right version
  • c563759 [LOCAL] Bump git checkout cache key
  • 69ce989 Revert "[0.70.6] Bump version numbers"
  • 02a388f [0.70.6] Bump version numbers
  • ef29c9b [LOCAL] remove regression: unwanted @​jest/create-cache-key-function dependency
  • 9bcc5e0 [LOCAL] Bump CLI to 9.3.2
  • 11473c3 Add support Promise.any out of box (#35080)
  • 3f1c55b Update ruby codegen to cleanup build folder. (#34398)
  • 35fa47b [0.70.5] Bump version numbers
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by fb, a new releaser for react-native since your current version.


Updates babel-jest from 22.1.0 to 29.3.1

Release notes

Sourced from babel-jest's releases.

v29.3.1

Fixes

  • [jest-config] Do not warn about preset in ProjectConfig (#13583)

Performance

  • [jest-transform] Defer creation of cache directory (#13420)

v29.3.0

Features

  • [jest-runtime] Support WebAssembly (Wasm) imports in ESM modules (#13505)

Fixes

  • [jest-config] Add config validation for projects option (#13565)
  • [jest-mock] Treat cjs modules as objects so they can be mocked (#13513)
  • [jest-worker] Throw an error instead of hanging when jest workers terminate unexpectedly (#13566)

Chore & Maintenance

  • [@jest/transform] Update convert-source-map (#13509)
  • [docs] Mention toStrictEqual in UsingMatchers docs. (#13560)

New Contributors

Full Changelog: https://github.com/facebook/jest/compare/v29.2.2...v29.3.0

v29.2.2

Fixes

  • [@jest/test-sequencer] Make sure sharding does not produce empty groups (#13476)
  • [jest-circus] Test marked as todo are shown as todo when inside a focussed describe (#13504)
  • [jest-mock] Ensure mock resolved and rejected values are promises from correct realm (#13503)
  • [jest-snapshot] Don't highlight passing asymmetric property matchers in snapshot diff (#13480)

Chore & Maintenance

  • [docs] Update link to Jest 28 upgrade guide in error message (#13483)
  • [jest-runner, jest-watcher] Update emittery (#13490)

New Contributors

... (truncated)

Changelog

Sourced from babel-jest's changelog.

29.3.1

Fixes

  • [jest-config] Do not warn about preset in ProjectConfig (#13583)

Performance

  • [jest-transform] Defer creation of cache directory (#13420)

29.3.0

Features

  • [jest-runtime] Support WebAssembly (Wasm) imports in ESM modules (#13505)

Fixes

  • [jest-config] Add config validation for projects option (#13565)
  • [jest-mock] Treat cjs modules as objects so they can be mocked (#13513)
  • [jest-worker] Throw an error instead of hanging when jest workers terminate unexpectedly (#13566)

Chore & Maintenance

  • [@jest/transform] Update convert-source-map (#13509)
  • [docs] Mention toStrictEqual in UsingMatchers docs. (#13560)

29.2.2

Fixes

  • [@jest/test-sequencer] Make sure sharding does not produce empty groups (#13476)
  • [jest-circus] Test marked as todo are shown as todo when inside a focussed describe (#13504)
  • [jest-mock] Ensure mock resolved and rejected values are promises from correct realm (#13503)
  • [jest-snapshot] Don't highlight passing asymmetric property matchers in snapshot diff (#13480)

Chore & Maintenance

  • [docs] Update link to Jest 28 upgrade guide in error message (#13483)
  • [jest-runner, jest-watcher] Update emittery (#13490)

29.2.1

Features

  • [@jest/globals, jest-mock] Add jest.Spied* utility types (#13440)

Fixes

  • [jest-environment-node] make globalThis.performance writable for Node 19 and fake timers (#13467)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by simenb, a new releaser for babel-jest since your current version.


Updates babel-preset-react-native from 4.0.0 to 5.0.2

Commits


Updates jest from 22.1.4 to 29.3.1

Release notes

Sourced from jest's releases.

v29.3.1

Fixes

  • [jest-config] Do not warn about preset in ProjectConfig (#13583)

Performance

  • [jest-transform] Defer creation of cache directory (#13420)

v29.3.0

Features

  • [jest-runtime] Support WebAssembly (Wasm) imports in ESM modules (#13505)

Fixes

  • [jest-config] Add config validation for projects option (#13565)
  • [jest-mock] Treat cjs modules as objects so they can be mocked (#13513)
  • [jest-worker] Throw an error instead of hanging when jest workers terminate unexpectedly (#13566)

Chore & Maintenance

  • [@jest/transform] Update convert-source-map (#13509)
  • [docs] Mention toStrictEqual in UsingMatchers docs. (#13560)

New Contributors

Full Changelog: https://github.com/facebook/jest/compare/v29.2.2...v29.3.0

v29.2.2

Fixes

  • [@jest/test-sequencer] Make sure sharding does not produce empty groups (#13476)
  • [jest-circus] Test marked as todo are shown as todo when inside a focussed describe (#13504)
  • [jest-mock] Ensure mock resolved and rejected values are promises from correct realm (#13503)
  • [jest-snapshot] Don't highlight passing asymmetric property matchers in snapshot diff (#13480)

Chore & Maintenance

  • [docs] Update link to Jest 28 upgrade guide in error message (#13483)
  • [jest-runner, jest-watcher] Update emittery (#13490)

New Contributors

... (truncated)

Changelog

Sourced from jest's changelog.

29.3.1

Fixes

  • [jest-config] Do not warn about preset in ProjectConfig (#13583)

Performance

  • [jest-transform] Defer creation of cache directory (#13420)

29.3.0

Features

  • [jest-runtime] Support WebAssembly (Wasm) imports in ESM modules (#13505)

Fixes

  • [jest-config] Add config validation for projects option (#13565)
  • [jest-mock] Treat cjs modules as objects so they can be mocked (#13513)
  • [jest-worker] Throw an error instead of hanging when jest workers terminate unexpectedly (#13566)

Chore & Maintenance

  • [@jest/transform] Update convert-source-map (#13509)
  • [docs] Mention toStrictEqual in UsingMatchers docs. (#13560)

29.2.2

Fixes

  • [@jest/test-sequencer] Make sure sharding does not produce empty groups (#13476)
  • [jest-circus] Test marked as todo are shown as todo when inside a focussed describe (#13504)
  • [jest-mock] Ensure mock resolved and rejected values are promises from correct realm (#13503)
  • [jest-snapshot] Don't highlight passing asymmetric property matchers in snapshot diff (#13480)

Chore & Maintenance

  • [docs] Update link to Jest 28 upgrade guide in error message (#13483)
  • [jest-runner, jest-watcher] Update emittery (#13490)

29.2.1

Features

  • [@jest/globals, jest-mock] Add jest.Spied* utility types (#13440)

Fixes

  • [jest-environment-node] make globalThis.performance writable for Node 19 and fake timers (#13467)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by simenb, a new releaser for jest since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/pentarex/react-native-gallery-manager/network/alerts).