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.

Sign up for GitHub

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

Jump to bottom

Update packages (major) #6773

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update packages (major) #6773

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 25, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@google-cloud/datastore 8.5.0 -> 9.0.0 age adoption passing confidence dependencies major
archiver 6.0.1 -> 7.0.1 age adoption passing confidence devDependencies major
codemirror 5.65.16 -> 6.0.1 age adoption passing confidence devDependencies major
css-loader 6.10.0 -> 7.1.2 age adoption passing confidence devDependencies major
css-minimizer-webpack-plugin 6.0.0 -> 7.0.0 age adoption passing confidence devDependencies major
del 6.1.1 -> 7.1.0 age adoption passing confidence devDependencies major
eslint (source) 8.56.0 -> 9.3.0 age adoption passing confidence devDependencies major
gulp (source) 4.0.2 -> 5.0.0 age adoption passing confidence devDependencies major
husky 7.0.4 -> 9.0.11 age adoption passing confidence devDependencies major
linkifyjs (source) 2.1.9 -> 4.1.3 age adoption passing confidence dependencies major
lru-cache 6.0.0 -> 10.2.2 age adoption passing confidence dependencies major
marked (source) 2.1.3 -> 12.0.2 age adoption passing confidence devDependencies major
node (source) 18.x -> 20.x age adoption passing confidence engines major
node 18-alpine -> 20-alpine age adoption passing confidence final major
node-fetch 2.7.0 -> 3.3.2 age adoption passing confidence dependencies major
p-queue 6.6.2 -> 8.0.1 age adoption passing confidence dependencies major
supertest 6.3.4 -> 7.0.0 age adoption passing confidence devDependencies major
webpack-build-notifier 2.3.0 -> 3.1.0 age adoption passing confidence devDependencies major

Release Notes

googleapis/nodejs-datastore (@​google-cloud/datastore)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • An existing method UpdateVehicleLocation is removed from service VehicleService (#​1248)
Features
Bug Fixes
  • An existing method UpdateVehicleLocation is removed from service VehicleService (#​1248) (ba79118)
  • Read time should be used for transaction reads (#​1171) (73a0a39)

v8.7.0

Compare Source

Features
  • Add several fields to manage state of database encryption update (#​1243) (5d28cda)

v8.6.0

Compare Source

Features
  • Add new types ExplainOptions, ExplainMetrics, PlanSummary, ExecutionStats (#​1241) (6c409d5)
  • Nodejs transaction redesign feature branch (#​1235) (1585d4a)
Bug Fixes
archiverjs/node-archiver (archiver)

v7.0.1

Compare Source

What’s changed

Maintenance

Dependency updates

v7.0.0

Compare Source

What’s changed

Breaking changes

Dependency updates

v6.0.2

Compare Source

What’s changed

Maintenance

Dependency updates

codemirror/basic-setup (codemirror)

v6.0.1

Compare Source

Bug fixes

Work around limitations in tree-shaking software that prevented basicSetup from being removed when unused.

v6.0.0

Compare Source

Breaking changes

Change the package name from @codemirror/example-setup to just codemirror.

The package no longer exports EditorState (since that is no longer necessary to set up a basic editor).

New features

The new minimalSetup export provides a minimal set of editor extensions.

webpack-contrib/css-loader (css-loader)

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

Features
  • added the getJSON option to output CSS modules mapping (#​1577) (af834b4)

v7.0.0

Compare Source

⚠ BREAKING CHANGES
  • The modules.namedExport option is true by default if you enable the esModule option

Migration guide:

Before:

import style from "./style.css";

console.log(style.myClass);

After:

import * as style from "./style.css";

console.log(style.myClass);
  • The modules.exportLocalsConvention has the value as-is when the modules.namedExport option is true and you don't specify a value
  • Minimum supported webpack version is 5.27.0
  • Minimum supported Node.js version is 18.12.0
Features
  • The modules.namedExports option works fine with any modules.exportLocalsConvention values (f96a110)
  • Added dashed variants for the modules.exportLocalsConvention options (40e1668)

v6.11.0

Compare Source

Features
Bug Fixes
webpack-contrib/css-minimizer-webpack-plugin (css-minimizer-webpack-plugin)

v7.0.0

Compare Source

⚠ BREAKING CHANGES
sindresorhus/del (del)

v7.1.0

Compare Source

v7.0.0

Compare Source

Breaking
  • Require Node.js 14 (#​143) 106d7d8
  • This package is now pure ESM. Please read this.
  • Moved from a default export to named exports:
    • require('del') → import {deleteAsync} from 'del'
    • require('del').sync → import {deleteSync} from 'del'
eslint/eslint (eslint)

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

v8.57.0

Compare Source

Features

  • 1120b9b feat: Add loadESLint() API method for v8 (#​18098) (Nicholas C. Zakas)
  • dca7d0f feat: Enable eslint.config.mjs and eslint.config.cjs (#​18066) (Nitin Kumar)

Bug Fixes

  • 2196d97 fix: handle absolute file paths in FlatRuleTester (#​18064) (Nitin Kumar)
  • 69dd1d1 fix: Ensure config keys are printed for config errors (#​18067) (Nitin Kumar)
  • 9852a31 fix: deep merge behavior in flat config (#​18065) (Nitin Kumar)
  • 4c7e9b0 fix: allow circular references in config (#​18056) (Milos Djermanovic)

Documentation

Chores

gulpjs/gulp (gulp)

v5.0.0

Compare Source

We've tried to provide a high-level changelog for gulp v5 below, but it
doesn't contain all changes from the 60+ dependencies that we maintain.

Please see individual changelogs to drill down
into all changes that were made.

⚠ BREAKING CHANGES
  • Drop support for Node.js <10.13
  • Default stream encoding to UTF-8
  • Standardized on anymatch library for globbing paths. All globs should work the same between src and watch now!
  • Removed support for ordered globs. This aligns with the chokidar globbing implementation. If you need your globs to be ordered, you can use ordered-read-stream
  • All globs and paths are normalized to unix-like filepaths
  • Only allow JS variants for .gulp.* config files
  • Removed support for alpha releases of v4 from gulp-cli
  • Removed the --verify flag
  • Renamed the --require flag to --preload to avoid conflicting with Node.js flags
  • Removed many legacy and deprecated loaders
  • Upgrade to chokidar v3
  • Clone Vinyl objects with stream contents using teex, but no longer wait for all streams to flow before cloned streams will receive data
  • Stop using process.umask() to make directories, instead falling back to Node's default mode
  • Throw on non-function, non-string option coercers
  • Drop support of Node.js snake_case flags
  • Use a Symbol for attaching the gulplog namespace to the store
  • Use a Symbol for attaching the gulplog store to the global
  • Use sha256 to hash the v8flags cache into a filename
Features
  • Streamlined the dependency tree
  • Switch all streams implementation to Streamx
  • Rewrote glob-stream to use a custom directory walk that relies on newer Node.js features and is more performant than old implementation
  • Implement translation support for all CLI messages and all messages passing through gulplog
  • Allow users to customize or remove the timestamp from their logs
  • Upgraded gulplog to v2. Messages logged via v1 will also display a deprecated warning. Plugins should update to v2 as the community upgrades to gulp 5
  • Added support for gulpile.cjs and gulpfile.mjs
  • Add support for swc, esbuild, sucrase, and mdx loaders
  • Provide an ESM export (#​2760) (b00de68)
  • Support sourcemap handling on streaming Vinyl contents
  • Support extends syntax for .gulp.* config file
  • Allow overriding gulpfile and preloads via .gulp.* config file
Bug Fixes
  • Resolve bugs related to symlinks on various platforms
  • Resolved some reported ReDoS CVEs and improved performance in glob-parent
  • Rework errors surfaced when encountering files or symlinks when trying to create directories
  • Ensure watch allows japanese characters in globs (72668c6)
  • Ensure watch does not trigger on negated globs (72668c6)
  • Improve handling of BOM at the beginning of a stream
  • Properly handle function coercer in array of option coercers
  • Fork to-absolute-glob to:
    • Check negative patterns before trimming
    • Ensure glob-like characters are escaped in cwd & root options
    • Resolve ../ at the beginning of globs
Miscellaneous Chores
  • Remove lazystream dependency
  • Updated various stream test suites to test against Node.js core stream, readable-stream, and streamx
  • Normalize repository, dropping node <10.13 support (#​2758) (72668c6)
Individual Changelogs

We created and maintain various projects that gulp depends upon. You can find their changelogs linked below:

typicode/husky (husky)

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

  • Enhanced security with CI and npm --provenance for safer publishing.
  • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
  • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
  • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
  • Modified behavior when .git is missing; it now triggers a warning instead of failure.
  • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
  • Updated the Husky API for module usage.
  • Transitioned to ESM for module usage.
  • Dropped support for Node 14 and 16.
  • Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test

v8.0.3

Compare Source

  • fix: add git not installed message #​1208

v8.0.2

Compare Source

  • docs: remove deprecated npm set-script

v8.0.1

Compare Source

  • fix: use POSIX equality operator

v8.0.0

Compare Source

What's Changed

Feats
Fixes
Docs
Chore
Hypercontext/linkifyjs (linkifyjs)

v4.1.3

Compare Source

  • Fix HTML entity & symbol double-encoding in linkify-html
  • Support for full-width brackets, full-width less-than/greater-than signs and corner bracket as delimiters

v4.1.2

Compare Source

  • Ensure linkify.find respects validate option

v4.1.1

Compare Source

  • Slightly simpler TLDs encoding/parsing
  • Fix jsdoc in linkify-react
  • Improved parsing of URLs with symbols
  • Ensure function options get called with unformatted href

v4.1.0

Compare Source

  • Drop support for Safari 10
  • Reduce core bundle file size by ~30%
  • Restore support for email address with scheme local part
  • Allow hashtags with emojis

v4.0.2

Compare Source

  • Fix email address detection with domains containing numbers

v4.0.1

Compare Source

  • Restore nl2br option for linkify-html
  • Fixed duplicate key warning in linkify-react with multiple children

v4.0.0

Compare Source

BREAKING CHANGES
  • Removed deprecated linkifyjs/string, linkifyjs/html, linkifyjs/plugins/*
    packages. Use linkify-string, linkify-html and linkify-plugin-* instead.
  • Refactored scanner internals break custom link plugins created with Linkify v3
  • Links that begin with mailto: now have type url instead of email
  • Drop official IE 11 support
Added
  • linkify-plugin-ip plugin for detecting IPv4 and IPv6 addresses
  • linkify-plugin-keyword plugin for detecting arbitrary keywords
  • linkify.find() function accepts an options argument for output formatting
  • New render option to override link rendering
  • Second optionalSlashSlash argument for registerCustomProtocol to allow links that don't require // after scheme:
  • Link token methods toFormattedString(options), toFormattedHref(options) and toFormattedObject(options) that accept a linkify.Options object
  • More granular scanner tokens for improved plugin flexibility
  • linkify-react: New as property (alias for tagName)
Fixed
  • Improved link detection with mixed languages
  • Consistent option availability across interfaces (including truncate)
  • linkify-html: Improved HTML entity parsing

v3.0.5

Compare Source

  • Fix potential Cross-Site Scripting issue when using linkify-html

v3.0.4

Compare Source

  • Expose ES6 modules with "module" field in package.json

v3.0.3

Compare Source

  • Add linkifyjs ES6 module build

v3.0.2

Compare Source

  • Correctly detect hashtags with underscores
  • Fix plugin import bug
  • Fix linkify-string and linkify-html type declarations

v3.0.1

Compare Source

  • Fix React component type declarations
  • Include LICENSE file in all published packages

v3.0.0

Compare Source

BREAKING CHANGES
  • React, jQuery and Element interfaces moved to dedicated packages at linkify-react,linkify-jquery and linkify-element respectively:
  • Remove default class="linkified" from all discovered links. Opt back in by setting the className option: 
    linkifyStr(str, { className: "linkified" });
  • Remove default target="_blank" attribute for discovered URLs. Opt back in by setting the target option: 
    linkifyHtml(str, {
  target: (href, type) => type === "url" && "_blank",
});
  • React component: Remove outer <span> tag wrapper in favour of tag-less React.Fragment for React >=16. To opt back-in, set tagName='span': 
    <Linkify tagName="span">{content}</Linkify>
  • AMD module interface is no longer provided. Use an ESM bundler instead

Configuration

📅 Schedule: Branch creation - "after 4am on sunday" (UTC), 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 force-pushed the renovate/major-packages branch 2 times, most recently from 4707842 to d328514 Compare March 6, 2024 08:28
@renovate renovate bot force-pushed the renovate/major-packages branch from d328514 to 0c307bf Compare March 10, 2024 04:23
@renovate renovate bot force-pushed the renovate/major-packages branch 2 times, most recently from 2df51cd to f5134b0 Compare April 4, 2024 21:05
@renovate renovate bot force-pushed the renovate/major-packages branch from f5134b0 to 8be9fa2 Compare April 5, 2024 21:32
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 5, 2024 •
edited

⚠ 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 click 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @babel/eslint-parser@7.23.10
npm ERR! Found: eslint@9.2.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.2.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.2.0
npm ERR!   3 more (eslint-config-google, eslint-config-prettier, eslint-plugin-prettier)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.23.10
npm ERR! node_modules/@babel/eslint-parser
npm ERR!   dev @babel/eslint-parser@"7.23.10" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@8.57.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.23.10
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     dev @babel/eslint-parser@"7.23.10" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-07T12_58_42_174Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-packages branch 2 times, most recently from c1def02 to cde720d Compare April 10, 2024 17:21
@renovate renovate bot force-pushed the renovate/major-packages branch 5 times, most recently from 40a44df to 6ece904 Compare April 25, 2024 19:10
@renovate renovate bot force-pushed the renovate/major-packages branch 2 times, most recently from 78b93cf to 72b9fb5 Compare May 3, 2024 22:32
@renovate renovate bot force-pushed the renovate/major-packages branch from 72b9fb5 to b9cf646 Compare May 7, 2024 12:58
@renovate renovate bot force-pushed the renovate/major-packages branch from b9cf646 to 57671b7 Compare May 18, 2024 00:28
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 18, 2024 •
edited

⚠️ 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 click 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @babel/eslint-parser@7.23.10
npm ERR! Found: eslint@9.3.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.3.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.3.0
npm ERR!   3 more (eslint-config-google, eslint-config-prettier, eslint-plugin-prettier)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.23.10
npm ERR! node_modules/@babel/eslint-parser
npm ERR!   dev @babel/eslint-parser@"7.23.10" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@8.57.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.23.10
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     dev @babel/eslint-parser@"7.23.10" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-29T07_30_16_612Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-packages branch 3 times, most recently from 8a4adae to ae9840d Compare May 27, 2024 18:09
@renovate renovate bot force-pushed the renovate/major-packages branch from ae9840d to feb7dd3 Compare May 29, 2024 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants