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) #39

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

Conversation

renovate[bot]
Copy link

@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/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/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 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Jan 9, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5ff62dd to 04b26ee Compare January 9, 2020 20:25
@renovate renovate bot changed the title Update dependency @semantic-release/git to v8 Update semantic-release monorepo (major) Jan 9, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 19a452c to 5e907b8 Compare January 15, 2020 18:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 64ae4c8 to 984069a Compare January 28, 2020 16:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 984069a to 7a98d69 Compare January 31, 2020 16:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 2016f92 to 9db98f3 Compare February 17, 2020 19:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9db98f3 to ef34792 Compare May 2, 2020 12:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ef34792 to 12d6aaf Compare June 30, 2020 17:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 12d6aaf to b4cad84 Compare October 25, 2020 20:05
@renovate renovate bot changed the title Update semantic-release monorepo (major) chore(deps): update semantic-release monorepo (major) Oct 25, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b4cad84 to 3ca30c9 Compare October 18, 2021 18:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3ca30c9 to e84276b Compare March 7, 2022 16:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e84276b to ace7007 Compare June 18, 2022 21:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ace7007 to 8ec2a01 Compare September 25, 2022 14:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8ec2a01 to 4c85288 Compare March 24, 2023 18:00
@renovate
Copy link
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants