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 semantic-release monorepo (major) #75

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2020

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 3.0.6 -> 6.0.3 age adoption passing confidence
@semantic-release/exec 3.3.8 -> 6.0.3 age adoption passing confidence
@semantic-release/git 7.0.18 -> 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
semantic-release/exec (@​semantic-release/exec)

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
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
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15

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.

@ghost
Copy link

ghost commented Jan 9, 2020

Congratulations 🎉. DeepCode analyzed your code in 0.799 seconds and we found no issues. Enjoy a moment of no bugs ☀️.

👉 View analysis in DeepCode’s Dashboard | Configure the bot

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fb325bd to db1b796 Compare January 9, 2020 19:53
@renovate renovate bot changed the title fix(deps): update dependency @semantic-release/exec to v4 fix(deps): update semantic-release monorepo (major) Jan 9, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 293093f to a3c27b3 Compare January 15, 2020 18:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 11ddb3f to 95ed17d Compare January 22, 2020 18:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 11 times, most recently from f1ba81a to c8341e5 Compare January 31, 2020 16:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 79b4264 to dde3be6 Compare February 13, 2020 01:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dde3be6 to 80205be Compare February 17, 2020 19:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b64bdf0 to 36773a4 Compare May 5, 2020 20:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 7 times, most recently from efb08ba to 51a795f Compare May 20, 2020 00:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from f9ebc8e to 75cd5e8 Compare May 28, 2020 20:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 385a34a to 000b384 Compare June 8, 2020 21:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 000b384 to a5b27cc Compare June 9, 2020 21:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 952643f to 69daae7 Compare June 25, 2020 16:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 69daae7 to be89875 Compare July 7, 2020 23:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from be89875 to f15aea6 Compare October 28, 2020 10:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f15aea6 to 862d9b7 Compare January 7, 2021 07:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 862d9b7 to 2796fca Compare October 18, 2021 20:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2796fca to 8002d67 Compare March 7, 2022 10:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8002d67 to 84222de Compare June 18, 2022 20:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 84222de to 23a22eb Compare September 25, 2022 13:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 23a22eb to a5e5c96 Compare March 16, 2023 10:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a5e5c96 to f09b102 Compare March 24, 2023 20:42
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

⚠ 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
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

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