Skip to content
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.

chore(deps-dev): Bump semantic-release, @semantic-release/commit-analyzer, @semantic-release/git, @semantic-release/github, @semantic-release/npm and @semantic-release/release-notes-generator #499

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 1, 2021

Bumps semantic-release, @semantic-release/commit-analyzer, @semantic-release/git, @semantic-release/github, @semantic-release/npm and @semantic-release/release-notes-generator. These dependencies needed to be updated together.
Updates semantic-release from 17.4.7 to 18.0.0

Release notes

Sourced from semantic-release's releases.

v18.0.0

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

v18.0.0-beta.8

18.0.0-beta.8 (2021-09-17)

Bug Fixes

  • plugins: upgraded to stable versions of the plugins (d5be46e)

v18.0.0-beta.7

18.0.0-beta.7 (2021-09-03)

Bug Fixes

  • plugins: upgraded to the beta versions of the commit-analyzer and release-notes-generator plugins (d945374)

v18.0.0-beta.6

18.0.0-beta.6 (2021-09-03)

Bug Fixes

  • npm: upgraded to the beta version of the npm plugin (#2103) (995469f)

v18.0.0-beta.5

18.0.0-beta.5 (2021-09-03)

Bug Fixes

  • error: upgraded to the beta of the error plugin (10fb716)

v18.0.0-beta.4

18.0.0-beta.4 (2021-09-03)

Bug Fixes

  • release-notes-generator: updated to the beta of the plugin (5c68d20), closes #2055

v18.0.0-beta.3

... (truncated)

Commits
  • 66cc2b4 feat(node-version): raised the minimum required version to v14.17 (#2132)
  • 1632e1a chore(deps): update dependency dockerode to v3.3.1 (#2113)
  • 0390af3 chore(deps): update dependency sinon to v11.1.2 (#2108)
  • e58b76e chore(deps): update dependency nock to v13.1.3 (#2107)
  • 5e228a1 chore(deps): update dependency codecov to v3.8.3 (#2106)
  • 23d2bc2 docs: fix broken link on github actions recipe (#2102)
  • b4200b0 ci(test): set node version explicitly in test job (#2092)
  • See full diff in compare view

Updates @semantic-release/commit-analyzer from 8.0.1 to 9.0.1

Release notes

Sourced from @​semantic-release/commit-analyzer's releases.

v9.0.1

9.0.1 (2021-09-18)

Bug Fixes

  • deps: update dependency import-from to v4 (#235) (2da0011)

v9.0.0

9.0.0 (2021-09-17)

Features

  • raise minimum version of Node to v14.17 (#248) (6eeaeb2)

BREAKING CHANGES

  • the minimum required version of node is now v14.17

v9.0.0-beta.3

9.0.0-beta.3 (2021-09-03)

Bug Fixes

v9.0.0-beta.2

9.0.0-beta.2 (2021-08-21)

Features

BREAKING CHANGES

  • @semantic-release/commit-analyzer is now a native ES Module
  • When setting the releaseRules option to a path, the path must include the .js extension, and the file must be an ES Module itself, exporting an array as default

Before:

{
  "plugins": [
    ["@semantic-release/commit-analyzer", {
      "preset": "angular",
</tr></table> 

... (truncated)

Commits
  • 2da0011 fix(deps): update dependency import-from to v4 (#235)
  • 62099d8 ci(engines): switched to ls-engines for enforcing engines compatibility (#266)
  • f1768f4 chore(deps): update dependency semantic-release to v18 (#265)
  • 6eeaeb2 feat: raise minimum version of Node to v14.17 (#248)
  • 5d7a717 chore(deps): lock file maintenance (#264)
  • 3686bc4 chore(deps): update dependency conventional-changelog-conventionalcommits to ...
  • cde5d76 chore(deps): lock file maintenance (#258)
  • 1053a1c chore(deps): lock file maintenance (#257)
  • 8246c4b chore(deps): lock file maintenance (#251)
  • 7f05e66 chore(deps): update dependency semantic-release to v17.4.7 (#256)
  • Additional commits viewable in compare view

Updates @semantic-release/git from 9.0.1 to 10.0.1

Release notes

Sourced from @​semantic-release/git's releases.

v10.0.1

10.0.1 (2021-10-30)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v3 (#295) (3e934d4)

v10.0.0

10.0.0 (2021-09-20)

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
Commits
  • 3e934d4 fix(deps): update dependency @​semantic-release/error to v3 (#295)
  • 01aad76 chore(deps): lock file maintenance (#304)
  • eae607b chore(deps): lock file maintenance (#302)
  • f9e1a09 chore(deps): lock file maintenance (#301)
  • 51280ff chore(deps): lock file maintenance (#300)
  • 7a41029 chore(deps): lock file maintenance (#299)
  • 7ab65f8 feat(node-version): raised the minimum required version to v14.17
  • 9105df6 chore(deps): lock file maintenance (#296)
  • fccf23d build(release.yml): set node-version to 16
  • 9d20879 chore(deps): lock file maintenance (#294)
  • Additional commits viewable in compare view

Updates @semantic-release/github from 7.2.3 to 8.0.1

Release notes

Sourced from @​semantic-release/github's releases.

v8.0.1

8.0.1 (2021-09-23)

Bug Fixes

  • deps: update dependency http-proxy-agent to v5 (#416) (a454f34)

v8.0.0

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17

v8.0.0-beta.1

8.0.0-beta.1 (2021-08-26)

Features

  • node-version: raised the minimum required version to v14.17 (#397) (c6edf42)

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17
Commits
  • a454f34 fix(deps): update dependency http-proxy-agent to v5 (#416)
  • d1e09d9 chore(deps): lock file maintenance
  • 501eeff chore(deps): lock file maintenance (#413)
  • 10e9542 build(release.yml): set node-version to 16
  • 589f1de chore(deps): update dependency semantic-release to v18.0.0 (#411)
  • 051659b feat(node-version): raised the minimum required version to v14.17 (#397) (#410)
  • f05d3bc chore(deps): lock file maintenance (#409)
  • e04d2eb chore(deps): lock file maintenance (#407)
  • 8c6fc88 chore(deps): lock file maintenance (#406)
  • 8689104 chore(deps): lock file maintenance (#399)
  • Additional commits viewable in compare view

Updates @semantic-release/npm from 7.1.3 to 8.0.2

Release notes

Sourced from @​semantic-release/npm's releases.

v8.0.2

8.0.2 (2021-10-20)

Bug Fixes

  • README: correct docs on authentication (#413) (f089d9d)

v8.0.1

8.0.1 (2021-10-18)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v3 (#402) (60832fb)

v8.0.0

8.0.0 (2021-09-17)

Features

  • node-version: raised the minimum required version to v14.17 (#387) (#399) (f65e49d)

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17

Co-authored-by: Matt Travi [email protected]

v8.0.0-beta.1

8.0.0-beta.1 (2021-08-30)

Features

  • node-version: raised the minimum required version to v14.17 (#387) (f78e383)

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17
Commits

Updates @semantic-release/release-notes-generator from 9.0.3 to 10.0.2

Release notes

Sourced from @​semantic-release/release-notes-generator's releases.

v10.0.2

10.0.2 (2021-09-18)

Bug Fixes

  • deps: update dependency conventional-changelog-writer to v5 (#212) (6724eca)

v10.0.1

10.0.1 (2021-09-17)

Bug Fixes

  • deps: update dependency import-from to v4 (#248) (bb00694)

v10.0.0

BREAKING CHANGES

  • the minimum required version of node is now v14.17.

Thanks

@​abel-mak

v10.0.0-beta.2

10.0.0-beta.2 (2021-09-03)

Features

  • updated the peer-dependency on semantic-release to v18 or above (d2f6e46)

v10.0.0-beta.1

10.0.0-beta.1 (2021-08-23)

Features

BREAKING CHANGES

  • the minimum required version of node is now v14.17.
Commits
  • 6724eca fix(deps): update dependency conventional-changelog-writer to v5 (#212)
  • 8d609ae build(release.yml): set node-version to 16
  • 383ade7 chore(deps): update dependency semantic-release to v18.0.0 (#277)
  • bb00694 fix(deps): update dependency import-from to v4 (#248)
  • d43efc6 feat: raise minimum version of Node to v14.17 (#267)
  • ac937b1 chore(deps): lock file maintenance (#276)
  • deadb8d chore(deps): update dependency conventional-changelog-conventionalcommits to ...
  • 8e5edc8 chore(deps): lock file maintenance (#274)
  • 00ac875 chore(deps): lock file maintenance (#273)
  • 6a4dca7 chore(deps): lock file maintenance (#262)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…yzer, @semantic-release/git, @semantic-release/github, @semantic-release/npm and @semantic-release/release-notes-generator

Bumps [semantic-release](https://github.com/semantic-release/semantic-release), [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer), [@semantic-release/git](https://github.com/semantic-release/git), [@semantic-release/github](https://github.com/semantic-release/github), [@semantic-release/npm](https://github.com/semantic-release/npm) and [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator). These dependencies needed to be updated together.

Updates `semantic-release` from 17.4.7 to 18.0.0
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v17.4.7...v18.0.0)

Updates `@semantic-release/commit-analyzer` from 8.0.1 to 9.0.1
- [Release notes](https://github.com/semantic-release/commit-analyzer/releases)
- [Commits](semantic-release/commit-analyzer@v8.0.1...v9.0.1)

Updates `@semantic-release/git` from 9.0.1 to 10.0.1
- [Release notes](https://github.com/semantic-release/git/releases)
- [Commits](semantic-release/git@v9.0.1...v10.0.1)

Updates `@semantic-release/github` from 7.2.3 to 8.0.1
- [Release notes](https://github.com/semantic-release/github/releases)
- [Commits](semantic-release/github@v7.2.3...v8.0.1)

Updates `@semantic-release/npm` from 7.1.3 to 8.0.2
- [Release notes](https://github.com/semantic-release/npm/releases)
- [Commits](semantic-release/npm@v7.1.3...v8.0.2)

Updates `@semantic-release/release-notes-generator` from 9.0.3 to 10.0.2
- [Release notes](https://github.com/semantic-release/release-notes-generator/releases)
- [Commits](semantic-release/release-notes-generator@v9.0.3...v10.0.2)

---
updated-dependencies:
- dependency-name: semantic-release
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@semantic-release/commit-analyzer"
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@semantic-release/git"
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@semantic-release/github"
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@semantic-release/npm"
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@semantic-release/release-notes-generator"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 1, 2021
@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot requested a review from Mini256 November 1, 2021 02:07
@ti-chi-bot ti-chi-bot added the contribution Indicates that the PR was contributed by an external member. label Nov 1, 2021
@ti-chi-bot
Copy link
Member

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a ti-community-infra member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-chi-bot ti-chi-bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 1, 2021
@ti-chi-bot
Copy link
Member

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale

@ti-chi-bot
Copy link
Member

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
contribution Indicates that the PR was contributed by an external member. dependencies Pull requests that update a dependency file lifecycle/rotten needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant