Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 27, 2018

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog 2.0.2 -> 6.0.3 age confidence
@semantic-release/exec 2.2.4 -> 7.1.0 age confidence
@semantic-release/git 5.0.0 -> 10.0.1 age confidence
babel-eslint 8.2.5 -> 10.1.0 age confidence
babel-loader 7.1.5 -> 10.0.0 age confidence
browser-sync (source) 2.24.5 -> 3.0.4 age confidence
commitizen 2.10.1 -> 4.3.1 age confidence
cz-conventional-changelog 2.1.0 -> 3.3.0 age confidence
eslint (source) 5.0.1 -> 9.37.0 age confidence
eslint-plugin-security 1.4.0 -> 3.0.1 age confidence
husky 0.14.3 -> 9.1.7 age confidence
lint-staged 7.2.0 -> 16.2.4 age confidence
metalsmith-markdown 0.2.2 -> 1.3.0 age confidence
metalsmith-sass 1.5.1 -> 2.0.0 age confidence
prettier (source) 1.13.7 -> 3.6.2 age confidence
pretty-quick 1.6.0 -> 4.2.2 age confidence
queue 4.4.2 -> 7.0.0 age confidence
rimraf 2.6.2 -> 6.0.1 age confidence
sonarwhal (source) 1.11.2 -> 2.0.0 age confidence
sort-package-json 1.15.0 -> 3.4.0 age confidence
uglifyjs-webpack-plugin 1.2.7 -> 2.2.0 age confidence
webpack 4.15.1 -> 5.102.1 age confidence
webpack-merge 4.1.3 -> 6.0.1 age confidence

Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (#​170) (5cf74e4)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v5.0.1

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore
  • require Node.js >=10.18 (5ffdf49)
BREAKING CHANGES
  • Require Node.js >= 10.18

v4.0.0

Compare Source

Features
  • require Node.js >=10.13 (1f483af)
BREAKING CHANGES
  • Require Node.js >= 10.13

v3.0.6

Compare Source

Bug Fixes
  • use correct peerDependencies for semantic-release (d36ee06)

v3.0.5

Compare Source

Bug Fixes

v3.0.4

Compare Source

Bug Fixes
  • package: update fs-extra to version 8.0.0 (50ed752)

v3.0.3

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (50789ef)

v3.0.2

Compare Source

Bug Fixes
  • package: update aggregate-error to version 2.0.0 (4007c72)

v3.0.1

Compare Source

Bug Fixes
  • use default value for null options (92608a3)

v3.0.0

Compare Source

Features
  • use cwd and env options passed by core (3173a68)
BREAKING CHANGES
  • require semantic-release >= 15.8.0

v2.1.2

Compare Source

Bug Fixes
  • package: update fs-extra to version 7.0.0 (a172379)

v2.1.1

Compare Source

Bug Fixes
  • factorise the verification code in a function (7300663)

v2.1.0

Compare Source

Features
  • options: adds changelogTitle option (f304bb0)

v2.0.3

Compare Source

Bug Fixes
  • fixes typos and wrong link in error message (3a09b0f)
semantic-release/exec (@​semantic-release/exec)

v7.1.0

Compare Source

Features
  • error: print more useful error for non-process failure (#​449) (a285bc5)

v7.0.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (#​188) (020eab0)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v5.0.0

Compare Source

chore
  • require Node.js >=10.18 (5984b6e)
BREAKING CHANGES
  • Require Node.js >= 10.18

v4.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (662a148)
  • use correct peerDependencies for semantic-release (fda4ecf)
  • package: update aggregate-error to version 2.0.0 (f18fbd4)
  • package: update execa to version 2.0.2 (6579bb3)
  • package: update execa to version 3.0.0 (ae40d3f)
  • return false in addChannel if step is skipped (d12a029)
  • return false in publish if package if step is skipped (48fc813)
Features
  • add addChannel plugin step (bdeda6c)
  • require Node.js >=10.13 (e4367de)
  • require Node.js >=8.15 (454965e)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Node.js => 8.15

v3.3.8

Compare Source

Bug Fixes
  • package: update execa to version 3.2.0 (1b89db4)
  • require Node.js >=8.16 (e520840)

v3.3.7

Compare Source

Bug Fixes
  • move invalid optionnal JSON output messsage to debug level (359844e)

v3.3.6

Compare Source

Bug Fixes
  • package: update parse-json to version 5.0.0 (9af96da)

v3.3.5

Compare Source

Bug Fixes

v3.3.4

Compare Source

Bug Fixes
  • package: update execa to version 2.0.0 (271a8fa)

v3.3.3

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (59ddda0)

v3.3.2

Compare Source

Bug Fixes
  • package: update aggregate-error to version 2.0.0 (d087866)

v3.3.1

Compare Source

Bug Fixes
  • return false in publish if package if step is skipped (745d0fa)

v3.3.0

Compare Source

Features

v3.2.0

Compare Source

Features
  • add dedicated command option for each step (1b66a36)

v3.1.3

Compare Source

Bug Fixes
  • package: update debug to version 4.0.0 (62a2576)

v3.1.2

Compare Source

Bug Fixes
  • package: update execa to version 1.0.0 (4bf6ad5)

v3.1.1

Compare Source

Bug Fixes
  • package: update execa to version 0.11.0 (e397274)

v3.1.0

Compare Source

Features

v3.0.3

Compare Source

Bug Fixes
  • stream command output to stdout and stderr (de16234)

v3.0.2

Compare Source

Bug Fixes
  • verify the cmd config independently for each steps (0fee76f)

v3.0.1

Compare Source

Bug Fixes
  • do not use execa.stdout.pipe as it closes the stream (7fae209)

v3.0.0

Compare Source

Features
  • log script output to stdout/stderr passed by semantic-release core (2ba5271)
BREAKING CHANGES
  • require semantic-release >= 15.9.0

v2.3.0

Compare Source

Features
  • use cwd and env options passed by core (cdb248f)
semantic-release/git (@​semantic-release/git)

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (7ab65f8)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

chore
  • require Node.js >=10.18 (4016fcc)
BREAKING CHANGES
  • Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (9c1dc67)
  • include deleted files in release commit (f59d20c)
  • package: update aggregate-error to version 2.0.0 (3eb8f60)
  • package: update execa to version 2.0.2 (9404d44)
  • package: update execa to version 3.0.0 (e6af5b4)
  • look for modified fiels to commit only if there files matching the globs (d97c030)
  • update globby to latest version (9e2b2e5)
Features
  • require Node.js >=10.13 (81955b8)
  • require Node.js >=8.15 (15356b1)
  • support branch parameter from semantic-release@​16.0.0 (02b1f6d)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15

v7.0.18

Compare Source

Bug Fixes
  • use correct debug scope (3323aac)

v7.0.17

Compare Source

Bug Fixes
  • package: update execa to version 3.2.0 (5132713)
  • require Node.js >=8.16 (7c9eb9a)

v7.0.16

Compare Source

Bug Fixes
  • package: update globby to version 10.0.0 (a93b846)

v7.0.15

Compare Source

Bug Fixes
  • package: update dir-glob to version 3.0.0 (2819d3b)

v7.0.14

Compare Source

Bug Fixes

v7.0.13

Compare Source

Bug Fixes
  • package: update execa to version 2.0.0 (39c4fd5)

v7.0.12

Compare Source

Bug Fixes
  • package: update fs-extra to version 8.0.0 (712d684)

v7.0.11

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (239eba1)

v7.0.10

Compare Source

Bug Fixes
  • package: update micromatch to version 4.0.0 (94e9e12)

v7.0.9

Compare Source

Bug Fixes
  • package: update p-reduce to version 2.0.0 (7ee4af9)

v7.0.8

Compare Source

Bug Fixes
  • update globby to latest version Pierre Vanduynslager committed (71be783)

v7.0.7

Compare Source

Bug Fixes
  • package: update aggregate-error to version 2.0.0 (f8857d5)

v7.0.6

Compare Source

Bug Fixes
  • look for modified fiels to commit only if there files matching the globs (7f26c5d)

v7.0.5

Compare Source

Bug Fixes
  • use default value for null options (e1aac3d)

v7.0.4

Compare Source

Bug Fixes
  • package: update debug to version 4.0.0 (ca9de5f)

v7.0.3

Compare Source

Bug Fixes
  • package: update execa to version 1.0.0 (a35f990)

v7.0.2

Compare Source

Bug Fixes
  • package: update execa to version 0.11.0 (20809c3)

v7.0.1

Compare Source

Bug Fixes
  • glob assets before running git ls-files (7eb2b3f)

v7.0.0

Compare Source

Features
  • use cwd and env options passed by core (1fab20e)
BREAKING CHANGES
  • require semantic-release >= 15.8.0

v6.0.2

Compare Source

Bug Fixes
  • package: update fs-extra to version 7.0.0 (54bd404)

v6.0.1

Compare Source

Bug Fixes
  • factorise the verification code in a function (fac45a3)

v6.0.0

Compare Source

Features
  • commit files from assets even if in they are in .gitignore (629dfc4)
BREAKING CHANGES
  • the .gitignore file is now ignored when adding files to the release commit

Each files matching a glob in assets will now be included in the release commit. The assets option has now to be configured to match exactly the the files that have to be commited, independently of the .gitignore file.

babel/babel-eslint (babel-eslint)

v10.1.0

Compare Source

v10.0.3

Compare Source

Fixes #​791, also eslint/eslint#12117

Some context: #​793 (comment)

We ended up going with @​JLHwung's PR #​794 which uses ESLint's deps instead of going with peerDeps since it really depends on the version being used and we don't want users to have to install it directly on their own.

babel-eslint is patching patches of the dependencies of ESLint itself so these kinds of issues have happened in the past. We'll need to look into figuring out how to have a more solid way of modifying behavior instead of this monkeypatching type of thing for future releases.

v10.0.2

Compare Source

Fixes #​772

v10.0.1

Compare Source

v10.0.1

The TypeAlias "conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.

v10.0.0

Compare Source

v10.0.0

Small breaking change: add a peerDependency starting from the ESLint version that added a parser feature that we were monkeypatching before (and drop that code). If already using ESLint 5 shouldn't be any different.

/* @​flow */
type Node<T> = { head: T; tail: Node<T> }

// or 

type File = {chunks: Array<Chunk>}
type Chunk = {file: File}
  • Update to test against ESLint 5, add a peerDependency: #​689
  • Drop monkeypatching behavior: #​690

v9.0.0

Compare Source

v9.0.0

We've released v7: https://twitter.com/left_pad/status/1034204330352500736, so this just updates babel-eslint to use those versions internally. That in itself doesn't break anything but:

  • Babel now supports the new decorators proposal by default, so we need to switch between the new and the old proposal. This is a breaking change.

To enable the legacy decorators proposal users should add a specific parser option:

{
  parserOptions: {
    ecmaFeatures: {
      legacyDecorators: true
    }
  }
}
  • Babel removed the support for Node 4 , so I propagated that here.

v8.2.6

Compare Source

babel/babel-loader (babel-loader)

v10.0.0

Compare Source

What's Changed

Breaking Changes
  • bump node requirement to ^18.20.0 || ^20.10.0 || >=22.0.0 and webpack requirement to >= 5.61.0 by @​JLHwung in #​1026
  • breaking: use output.hashFunction as loader cache hasher by @​JLHwung in #​1027
New Features
Bug Fixes
Docs
Dependencies
Internal

New Contributors

Full Changelog: babel/babel-loader@v9.1.3...v10.0.0

v9.2.1

Compare Source

What's Changed

Full Changelog: babel/babel-loader@v9.2.0...v9.2.1

v9.2.0

Compare Source

What's Changed

Full Changelog: babel/babel-loader@v9.1.3...v9.2.0

v9.1.3

Compare Source

Security dependency updates

New Contributors

Full Changelog: babel/babel-loader@v9.1.2...v9.1.3

v9.1.2

Compare Source

9.1.1 was a broken release, it didn't include all the commits.

Dependencies updates

Misc

New Contributors

Full Changelog: babel/babel-loader@v9.1.0...v9.1.2

v9.1.1

Compare Source

v9.1.0

Compare Source

New features

Full Changelog: babel/babel-loader@v9.0.1...v9.1.0

v9.0.1

Compare Source

Bug Fixes

Full Changelog: babel/babel-loader@v9.0.0...v9.0.1

v9.0.0

Compare Source

What's Changed

  • update hash method mechanism so it doesn't fail on a fips enabled machine by @​darmbrust in #​939
  • Require babel ^7.12.0 and Node.js >= 14.15.0 versions by @​JLHwung in #​956
  • Remove dependency on loader-utils and drop webpack 4 support by @​nied in #​942

New Contributors


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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-all-dev branch 4 times, most recently from 3d88be6 to 21cbb1b Compare September 3, 2018 00:14
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 32b0684 to 76cad3e Compare September 18, 2018 10:26
@renovate renovate bot force-pushed the renovate/major-all-dev branch 7 times, most recently from 5b6765d to 7123786 Compare October 1, 2018 16:31
@renovate renovate bot force-pushed the renovate/major-all-dev branch 4 times, most recently from e53e3c8 to de64ab6 Compare October 5, 2018 16:43
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from ceb8971 to b8be629 Compare October 15, 2018 22:10
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 0ecd0c7 to af56aa4 Compare October 25, 2018 23:32
@renovate renovate bot force-pushed the renovate/major-all-dev branch 6 times, most recently from 7452874 to 6a0b9a3 Compare October 31, 2018 11:50
@renovate renovate bot force-pushed the renovate/major-all-dev branch 5 times, most recently from 7f03152 to 4de8ba7 Compare July 11, 2025 11:56
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 34f49e6 to 4fe8922 Compare July 25, 2025 20:08
@renovate renovate bot force-pushed the renovate/major-all-dev branch 4 times, most recently from 630a17c to b6d5029 Compare August 10, 2025 14:00
@renovate renovate bot force-pushed the renovate/major-all-dev branch 5 times, most recently from db32e1a to 53f2abd Compare August 19, 2025 12:38
@renovate renovate bot force-pushed the renovate/major-all-dev branch from 53f2abd to 0d7cd27 Compare August 22, 2025 21:14
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from cde6cb5 to c91d684 Compare September 6, 2025 15:48
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 5e62223 to f733fea Compare September 25, 2025 18:51
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from d88129c to d86c4b2 Compare October 5, 2025 10:39
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from f5dd460 to e555af0 Compare October 11, 2025 08:34
@renovate renovate bot force-pushed the renovate/major-all-dev branch from e555af0 to e5e7afe Compare October 16, 2025 01:57
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.

0 participants