Skip to content
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

fix(deps): update all non-major dependencies #174

Merged
merged 1 commit into from Feb 22, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@fortawesome/fontawesome-svg-core (source) 6.2.1 -> 6.3.0 age adoption passing confidence dependencies minor
@fortawesome/free-brands-svg-icons (source) 6.2.1 -> 6.3.0 age adoption passing confidence dependencies minor
@fortawesome/free-regular-svg-icons (source) 6.2.1 -> 6.3.0 age adoption passing confidence dependencies minor
@fortawesome/free-solid-svg-icons (source) 6.2.1 -> 6.3.0 age adoption passing confidence dependencies minor
@next/bundle-analyzer 13.1.5 -> 13.1.6 age adoption passing confidence dependencies patch
@​vercel/og ^0.0.27 -> ^0.1.0 age adoption passing confidence dependencies minor
framer-motion 8.5.3 -> 8.5.5 age adoption passing confidence dependencies patch
lint-staged 13.1.0 -> 13.1.2 age adoption passing confidence devDependencies patch
next (source) 13.1.5 -> 13.1.6 age adoption passing confidence dependencies patch
node 18.13.0 -> 18.14.2 age adoption passing confidence volta minor
remark-emoji 3.0.2 -> 3.1.1 age adoption passing confidence devDependencies minor
shiki (source) ^0.12.1 -> ^0.14.0 age adoption passing confidence dependencies minor
typescript (source) 4.9.4 -> 4.9.5 age adoption passing confidence devDependencies patch
yarn 3.3.1 -> 3.4.1 age adoption passing confidence packageManager minor

Release Notes

FortAwesome/Font-Awesome

v6.3.0

Compare Source

Change log available at https://fontawesome.com/docs/changelog/

vercel/next.js

v13.1.6

Compare Source

Core Changes
  • Add debug info to static bailout message: #​45192
  • Fix dynamic no ssr with babel transform: #​45091
  • Fix React.lazy preloading during SSR: #​45160
  • Fix error overlay links in parenthesis: #​45155
  • Add build time error if error.js is missing "use client": #​44961
  • Show component stack in error overlay on hydration error: #​45089
  • Reduce component stack spacing for components without metadata: #​45218
  • Revert "Revert "Revert "Revert "Initial support for metadata (#​44729)"" (#​45113)"": #​45196
  • Update handling of autoscrolling on navigation in app: #​43845
  • perf: avoid sync re-renders when using next/link and next/image: #​45165
  • Support metadata icons field: #​45105
  • Add editor links to RSC build error: #​45179
  • misc: change strategy for link prefetch test: #​45234
  • Add handling for app/pages manifest race condition: #​45244
  • Update transform exports and tests: #​45251
  • Attach exports information in SWC transforms: #​45261
  • Update app cache handling in development: #​45248
  • TS plugin: warn about amp config in app: #​45254
  • Fix typo in TS plugin: #​45279
  • Allow metadata related exports in TS plugin: #​45282
  • build(cargo): update turbopack to turbopack-230125.1: #​45283
  • [edge] improve fetch stack traces in edge runtime: #​44750
  • Move router reducer to separate file: #​45236
  • add next.config.js options currently supported by turbopack: #​45309
  • Update debug logs for app cache: #​45291
  • Improved pnpm clean: #​45312
  • Fix:Manage Firefox and Safari Network error message: #​44929
  • build(cargo): update turbopack to turbopack-230126.1: #​45322
  • add pageExtensions as a supported turbopack option: #​45321
  • Ensure we warn for middleware with next export: #​45288
  • Add unit test for shouldHardNavigate: #​45303
  • Add unit test for redirect.ts: #​45223
  • Add test for fillCacheWithNewSubTreeData: #​45298
  • Add test for isNavigatingToNewRootLayout: #​45305
  • Remove unused optimistic tree parameters: #​45264
  • Ensure invalidateCacheBelowFlightSegmentPath file name is in line with the rest: #​45299
  • Resolve metadata fields: #​45237
  • Add turbopack route resolve handling: #​45314
  • Remove extra .ts from test file: #​45328
  • Add test for createOptimisticTree: #​45330
  • Clean up resolved todos: #​45332
  • add turbopackLoaders to config validation: #​45337
Documentation Changes
  • Update example test file name in cypress example: #​45146
  • chore: fix invalid-new-link error typo: #​45157
  • Update testing.md: #​45216
  • Update no-html-link-for-pages.md: #​45247
  • Update getting-started documentation: #​45284
Example Changes
  • Update README.md for examples/with-mqtt-js: #​45162
  • Pin library version in Convex example: #​45206
  • Updates with-supertokens example app: #​45214
Misc Changes
  • Re-prompt on invalid import alias: #​45194
  • create-next-app: warn if project dir isn't empty before prompts: #​45195
  • Add timeout for actions/cache restoring: #​45198
  • Update testing.md to reflect that we don't use yarn anymore: #​45185
  • fix: add src prefix on index page: #​45150
  • Ensure ctrl + c handling works with CNA prompts correctly: #​45205
  • Fix turbo cache miss due to depending on gitignored files: #​45166
  • Allow unit tests to be written in packages/next/src: #​45222
  • Run dev tests against default CNA templates: #​45211
  • Increase cache timeout for swc built files: #​45243
  • refactor(create-next-app): simplify import alias validation logic: #​45241
  • ci(workflow): notify new releases to vercel/turbo via repo_dispatch: #​45201
  • Revert "Fix new-error command": #​45221
  • Update flakey test cases: #​45290
  • Update flakey polyfills and acceptance tests: #​45313
  • Add docs on how to use MDX with app: #​44923
  • Update flakey fetch stack test: #​45318
  • Enable JS CNA tests for turbopack: #​45323
Credits

Huge thanks to @​MaxLeiter, @​CachorroC, @​ijjk, @​asadnq, @​huozhi, @​JanKaifer, @​ilyasmez, @​juliusmarminge, @​thomasballinger, @​tissawd, @​hanneslund, @​shuding, @​timneutkens, @​feedthejim, @​ClemensPaumgarten, @​kwonoj, @​Angelfire, @​rishabhpoddar, @​HyunseungLee-Travis, @​wbinnssmith, @​Schniz, @​ForsakenHarmony, @​wyattjoh, and @​dtrucs for helping!

framer/motion

v8.5.5

Compare Source

Fixed
  • Ensuring Animation.cancel() is called on finished WAAPI animations.

v8.5.4

Compare Source

Fixed
  • Reducing size of prop filtering.
okonet/lint-staged

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • allow re-enabling --stash when using the --diff option (99390c3)
nodejs/node

v18.14.2: 2023-02-21, Version 18.14.2 'Hydrogen' (LTS), @​MylesBorins

Compare Source

Notable Changes
Commits

v18.14.1: 2023-02-16, Version 18.14.1 'Hydrogen' (LTS), @​RafaelGSS prepared by @​juanarbol

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

  • CVE-2023-23918: Node.js Permissions policies can be bypassed via process.mainModule (High)
  • CVE-2023-23919: Node.js OpenSSL error handling issues in nodejs crypto library (Medium)
  • CVE-2023-23936: Fetch API in Node.js did not protect against CRLF injection in host headers (Medium)
  • CVE-2023-24807: Regular Expression Denial of Service in Headers in Node.js fetch API (Low)
  • CVE-2023-23920: Node.js insecure loading of ICU data through ICU_DATA environment variable (Low)

More detailed information on each of the vulnerabilities can be found in February 2023 Security Releases blog post.

This security release includes OpenSSL security updates as outlined in the recent
OpenSSL security advisory.

Commits

v18.14.0: 2023-02-02, Version 18.14.0 'Hydrogen' (LTS), @​BethGriggs prepared by @​juanarbol

Compare Source

Notable changes
Updated npm to 9.3.1

Based on the list of guidelines we've established on integrating npm and node,
here is a grouped list of the breaking changes with the reasoning as to why they
fit within the guidelines linked above. Note that all the breaking changes were
made in 9.0.0.
All subsequent minor and patch releases after npm@9.0.0 do not contain any
breaking changes.

Engines

Explanation: the node engines supported by npm@9 make it safe to allow npm@9 as the default in any LTS version of 14 or 16, as well as anything later than or including 18.0.0

  • npm is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0
Filesystem

Explanation: when run as root previous versions of npm attempted to manage file ownership automatically on the user's behalf. this behavior was problematic in many cases and has been removed in favor of allowing users to manage their own filesystem permissions

  • npm will no longer attempt to modify ownership of files it creates.
Auth

Explanation: any errors thrown from users having unsupported auth configurations will show npm config fix in the remediation instructions, which will allow the user to automatically have their auth config fixed.

  • The presence of auth related settings that are not scoped to a specific
    registry found in a config file is no longer supported and will throw errors.
Login

Explanation: the default auth-type has changed and users can opt back into the old behavior with npm config set auth-type=legacy. login and adduser have also been seperated making each command more closely match it's name instead of being aliases for each other.

  • Legacy auth types sso, saml & legacy have been consolidated into "legacy".
  • auth-type defaults to "web"
  • login and adduser are now separate commands that send different data to the registry.
  • auth-type config values web and legacy only try their respective methods,
    npm no longer tries them all and waits to see which one doesn't fail.
Tarball Packing

Explanation: previously using multiple ignore/allow lists when packing was an undefined behavior, and now the order of operations is strictly defined when packing a tarball making it easier to follow and should only affect users relying on the previously undefined behavior.

  • npm pack now follows a strict order of operations when applying ignore rules.
    If a files array is present in the package.json, then rules in .gitignore
    and .npmignore files from the root will be ignored.
Display/Debug/Timing Info

Explanation: these changes center around the display of information to the terminal including timing and debug log info. We do not anticipate these changes breaking any existing workflows.

  • Links generated from git urls will now use HEAD instead of master as the default ref.
  • timing has been removed as a value for --loglevel.
  • --timing will show timing information regardless of --loglevel, except when --silent.
  • When run with the --timing flag, npm now writes timing data to a file
    alongside the debug log data, respecting the logs-dir option and falling
    back to <CACHE>/_logs/ dir, instead of directly inside the cache directory.
  • The timing file data is no longer newline delimited JSON, and instead each run
    will create a uniquely named <ID>-timing.json file, with the <ID> portion
    being the same as the debug log.
  • npm now outputs some json errors on stdout. Previously npm would output
    all json formatted errors on stderr, making it difficult to parse as the
    stderr stream usually has logs already written to it.
Config/Command Deprecations or Removals

Explanation: install-links is the only config or command in the list that has an effect on package installs. We fixed a number of issues that came up during prereleases with this change. It will also only be applied to new package trees created without a package-lock.json file. Any install with an existing lock file will not be changed.

  • Deprecate boolean install flags in favor of --install-strategy.
  • npm config set will no longer accept deprecated or invalid config options.
  • install-links config defaults to "true".
  • node-version config has been removed.
  • npm-version config has been removed.
  • npm access subcommands have been renamed.
  • npm birthday has been removed.
  • npm set-script has been removed.
  • npm bin has been removed (use npx or npm exec to execute binaries).
Other notable changes
  • doc:
    • add parallelism note to os.cpus() (Colin Ihrig) #​45895
  • http:
    • join authorization headers (Marco Ippolito) #​45982
    • improved timeout defaults handling (Paolo Insogna) #​45778
  • stream:
    • implement finished() for ReadableStream and WritableStream (Debadree Chatterjee) #​46205
Commits

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 requested a review from tdkn January 8, 2023 17:03
@vercel
Copy link

vercel bot commented Jan 8, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
blog ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Feb 21, 2023 at 7:31PM (UTC)

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9f6ba48 to 2a1ad0a Compare January 9, 2023 12:33
@renovate renovate bot changed the title fix(deps): update dependency rehype-pretty-code to ^0.7.0 fix(deps): update all non-major dependencies Jan 9, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2a1ad0a to e145349 Compare January 9, 2023 17:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e145349 to 1b28f50 Compare January 9, 2023 21:41
@tdkn tdkn merged commit 923fb12 into main Feb 22, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch February 22, 2023 16:13
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.

None yet

1 participant