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

chore(deps): update semantic-release monorepo (major) #49

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 18, 2020

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 3.0.2 -> 6.0.3 age adoption passing confidence
@semantic-release/git 7.0.8 -> 10.0.1 age adoption passing 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)
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)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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-semantic-release-monorepo branch from 45a7793 to 41d4336 Compare February 9, 2020 08:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 41d4336 to 9c007d5 Compare February 22, 2020 09:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9c007d5 to 3fadeb6 Compare April 26, 2020 16:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3fadeb6 to 05461f0 Compare July 1, 2020 22:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 05461f0 to 237bbb0 Compare October 27, 2020 08:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 237bbb0 to e958d43 Compare October 18, 2021 16:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e958d43 to 1b3d125 Compare March 7, 2022 17:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dff94e5 to 48fdf9f Compare March 24, 2023 23:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 571a9a0 to f2f1f0d Compare June 2, 2023 21:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4e64c60 to d5187f4 Compare June 10, 2023 00:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from a9c2721 to 6ee8866 Compare July 5, 2023 04:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 1dcc01f to 730a65e Compare August 24, 2023 19:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 4fd0148 to f3c1348 Compare September 23, 2023 01:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f3c1348 to 87a25fd Compare September 24, 2023 19:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3558e79 to 61a4b01 Compare November 3, 2023 22:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 61a4b01 to 1f24414 Compare November 17, 2023 05:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 48b0bcc to 19dc05f Compare December 12, 2023 00:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 19dc05f to 8a4ce68 Compare December 12, 2023 07:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8a4ce68 to 9d41a32 Compare January 12, 2024 23:31
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