Skip to content

fix(deps): update dependency runtypes to v6.4.0 #3247

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 2, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
runtypes 6.3.1 -> 6.4.0 age adoption passing confidence

Release Notes

pelotom/runtypes

v6.4.0

Compare Source

Features

v6.3.2

Compare Source

Bug Fixes
  • Use globalThis instead of global (#​273)
Documentation
  • Add runtyping as a related library (#​271)

Configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 2, 2021

⚠ 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 check 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: react-front-end/package-lock.json
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Parcel v1 is no longer maintained. Please migrate to v2, which is published under the 'parcel' package. See https://v2.parceljs.org/getting-started/migration for details.
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 127
npm ERR! path /mnt/renovate/gh/openequella/openEQUELLA/oeq-ts-rest-api
npm ERR! command failed
npm ERR! command sh -c npm run build
npm ERR! > @openequella/[email protected] build
npm ERR! > rollup --config
npm ERR! sh: 1: rollup: not found

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-09-04T22_48_24_199Z-debug.log

@edalex-ian
Copy link
Member

Gah! That seems to have blown up big time on one of our uses of Union. 😞

Things keep breaking lately with runtypes. 😭

@PenghaiZhang
Copy link
Contributor

Gah! That seems to have blown up big time on one of our uses of Union.

Things keep breaking lately with runtypes.

Runtypes seems to make breaking changes more and more.

@renovate renovate bot changed the title fix(deps): update dependency runtypes to v6.3.2 fix(deps): update dependency runtypes to v6.4.0 Sep 4, 2021
@renovate renovate bot force-pushed the renovate/runtypes-6.x branch from db6023b to 9dd39ae Compare September 4, 2021 22:48
@PenghaiZhang
Copy link
Contributor

Probably can close this PR.

@edalex-ian
Copy link
Member

Closing in favour of #3391 and specifically the work in commit 22561ce

@edalex-ian edalex-ian closed this Sep 14, 2021
@edalex-ian edalex-ian deleted the renovate/runtypes-6.x branch September 14, 2021 04:10
@renovate
Copy link
Contributor Author

renovate bot commented Sep 14, 2021

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (6.4.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

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.

3 participants