Skip to content

chore(deps): update semantic-release monorepo#4

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/semantic-release-monorepo
Open

chore(deps): update semantic-release monorepo#4
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/semantic-release-monorepo

Conversation

@renovate

@renovate renovate Bot commented Nov 21, 2019

Copy link
Copy Markdown

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 3.0.5 -> 3.0.6 age adoption passing confidence
@semantic-release/commit-analyzer 7.0.0-beta.6 -> 7.0.0 age adoption passing confidence
@semantic-release/git 7.1.0-beta.9 -> 7.1.0-beta.11 age adoption passing confidence
@semantic-release/github 5.6.0-beta.4 -> 5.6.0-beta.7 age adoption passing confidence
@semantic-release/npm 6.0.0-beta.4 -> 6.0.0 age adoption passing confidence

Release Notes

semantic-release/changelog

v3.0.6

Compare Source

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

v7.0.0

Compare Source

Bug Fixes
  • use correct peerDependencies for semantic-release (4ff652f)
  • package: update import-from to version 3.0.0 (060dc29)
Features
  • add support for conventionalcommits preset (2b5ac0a)
  • allow to disable default release rules with release: false (ea2b204)
  • require Node.js >=10.13 (9f72907)
  • use globs instead of regexp for releases rules (fc9b28a)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Regexp are not supported anymore for property matching in the releaseRules option.

Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.

v7.0.0-beta.7

Compare Source

Features
  • require Node.js >=10.13 (9f72907)
BREAKING CHANGES
  • Require Node.js >= 10.13
semantic-release/git

v7.1.0-beta.11

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (9c1dc67)

v7.1.0-beta.10

Compare Source

Features
  • require Node.js >=10.13 (81955b8)
BREAKING CHANGES
  • Require Node.js >= 10.13
semantic-release/github

v5.6.0-beta.7

Compare Source

Bug Fixes
  • package: update http-proxy-agent to version 3.0.0 (e856c0f)
  • package: update https-proxy-agent to version 4.0.0 (e2a069f)

v5.6.0-beta.6

Compare Source

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

v5.6.0-beta.5

Compare Source

Bug Fixes
  • use the branch.main flag to determine is the release need the prerelease flag (7aaeb0f)
semantic-release/npm

v6.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (d97dee5)
  • package: update semver to version 6.3.0 (c515862)
  • add dist-tag to publish and add-channel logs (db6ccd2)
  • use correct peerDependencies for semantic-release (8b47e7b)
  • package: pin npm to 6.5.0 (ddab7b7)
  • package: update aggregate-error to version 2.0.0 (df53298)
  • package: update aggregate-error to version 3.0.0 (3e0d5d0)
  • package: update execa to version 3.0.0 (b1780c1)
  • package: update npm to version 6.8.0 (2b0492e)
  • package: update read-pkg to version 5.0.0 (877ce40)
  • package: update vulnerable dependencies (#​185) (a96c6da)
  • skip tarball move if config is cwd (a224497)
  • package: update execa to version 2.0.2 (d2932ba)
  • package: update registry-auth-token to version 4.0.0 (2868b2c)
  • add dist-tag to publish log (2de37a1)
  • Honor NPM_CONFIG_USERCONFIG setting (932ea5e)
  • package: update fs-extra to version 8.0.0 (bf603e5)
  • return false if the npm publish is skipped (4a41228)
  • return false in addChannel if package is not published on npm (5434bab)
Features
  • add addChannel plugin step (fb96126)
  • require Node.js >=10.13 (6426458)
  • require Node.js >=8.15 (4caf538)
  • support nextRelease.channel property in publish step (b8deba7)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Node.js => 8.15

v6.0.0-beta.9

Compare Source

Bug Fixes
  • include version in npm release URL (827fcb3)

v6.0.0-beta.8

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (d97dee5)

v6.0.0-beta.7

Compare Source

Bug Fixes
  • package: update semver to version 6.3.0 (c515862)

v6.0.0-beta.6

Compare Source

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

v6.0.0-beta.5

Compare Source

Bug Fixes
  • add dist-tag to publish and add-channel logs (db6ccd2)

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch from f4944df to cff3df9 Compare November 21, 2019 07:28
@renovate renovate Bot changed the title chore(deps): update semantic-release monorepo chore(deps): update dependency @semantic-release/commit-analyzer to v7.0.0-beta-.2 Nov 21, 2019
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch from cff3df9 to d3b39da Compare November 21, 2019 18:17
@renovate renovate Bot changed the title chore(deps): update dependency @semantic-release/commit-analyzer to v7.0.0-beta-.2 chore(deps): update semantic-release monorepo Nov 21, 2019
@renovate renovate Bot changed the title chore(deps): update semantic-release monorepo chore(deps): update dependency @semantic-release/changelog to v3.0.6 Nov 22, 2019
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch from d3b39da to 81cba99 Compare November 23, 2019 16:16
@renovate renovate Bot changed the title chore(deps): update dependency @semantic-release/changelog to v3.0.6 chore(deps): update semantic-release monorepo Nov 23, 2019
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 6 times, most recently from db38907 to e01edb8 Compare December 4, 2019 01:41
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 9 times, most recently from 76721b2 to 2bb8c34 Compare December 10, 2019 05:33
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from f811300 to 7c39752 Compare December 13, 2019 21:20
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 37fe776 to 2cf6bd4 Compare December 19, 2019 19:22
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from 0c7e490 to 1bd22c3 Compare January 9, 2020 20:01
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from 18b2f49 to 5488bb6 Compare January 15, 2020 18:55
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 5488bb6 to 8131f1e Compare January 22, 2020 18:25
@renovate renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 8131f1e to 5706d01 Compare January 27, 2020 17:10
@renovate

renovate Bot commented Mar 24, 2023

Copy link
Copy Markdown
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant