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

⬆️ Updates semantic-release monorepo (major) #272

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 5.0.1 -> 6.0.3 age adoption passing confidence
@semantic-release/commit-analyzer 8.0.1 -> 13.0.0 age adoption passing confidence
@semantic-release/git 9.0.0 -> 10.0.1 age adoption passing confidence
@semantic-release/github 7.2.3 -> 11.0.1 age adoption passing confidence
@semantic-release/npm 7.1.3 -> 12.0.1 age adoption passing confidence
@semantic-release/release-notes-generator 9.0.2 -> 14.0.2 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
semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are
    dropping support for previous major versions of those packages due to the breaking changes between
    majors. this only impacts your project if you are installing alongside semantic-release, so updating
    those packages to latest version should be the only change you need for this update. no action
    should be necessary if you are using default semantic-release config

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (f3358dd)
  • node-versions: dropped support for node v18 and v19 (0a23b82)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.1.0

Compare Source

Features

v11.0.0

Compare Source

Bug Fixes
  • config-loader: accounted for normalization of preset interfaces (3ff9458)
  • deps: update dependency conventional-commits-filter to v4 (99dcf7e)
Features
  • conventional-changelog-presets: supported new preset format (f3b88d3)
  • node-versions: raised the minimum node version to v18.17 and dropped v19 support (a681fbd)
BREAKING CHANGES
  • node-versions: the minimum required node version is now v18.17, v19 support has been dropped, and the minimum required in the v20 range is v20.6.1
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility

v10.0.4

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (a7201b6)

v10.0.3

Compare Source

Reverts
  • Revert "fix(deps): update dependency conventional-commits-parser to v5 (#​501)" (ab3ee9f), closes #​501
  • Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#​502)" (f21eb8e), closes #​502
  • Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#​504)" (c48b533), closes #​504

v10.0.2

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (#​501) (91cf4d5)

v10.0.1

Compare Source

Bug Fixes
  • deps: update dependency conventional-changelog-angular to v6 (#​460) (0607201)
  • deps: update dependency conventional-commits-filter to v3 (#​461) (97d683f)
  • deps: update dependency conventional-commits-parser to v4 (#​462) (5d94efa)

v10.0.0

Compare Source

Code Refactoring
Features
  • deps: raised the peer-dependency requirement on semantic-release to v20.1.0 (e1ab8ea)
  • node-versions: raised the minimum required node version to v18 (affeb23)
BREAKING CHANGES
  • deps: the minimum required version of semantic-release is now v20.1.0 in order to support
    loading ESM plugins
  • node-versions: the minimum required version of node is now v18
  • esm: @semantic-release/commit-analyzer is now a native ES Module. It has named exports
    for each plugin hook (analyzeCommits)

v9.0.2

Compare Source

Bug Fixes
  • bump conventional commits parser to version 3.2.3 (#​289) (fc0a88a)

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of node is now v14.17
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
semantic-release/github (@​semantic-release/github)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported

v9.2.6

Compare Source

Bug Fixes

v9.2.5

Compare Source

Bug Fixes

v9.2.4

Compare Source

Bug Fixes

v9.2.3

Compare Source

Bug Fixes

v9.2.2

Compare Source

Bug Fixes

v9.2.1

Compare Source

v9.2.0

Compare Source

Features

v9.1.0

Compare Source

Features
  • releaseNameTemplate and releaseBodyTemplate options for customizing release body and name (#​704) (9e2678c)

v9.0.7

Compare Source

Bug Fixes

v9.0.6

Compare Source

Bug Fixes

v9.0.5

Compare Source

Bug Fixes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

BREAKING CHANGES
  • @semantic-release/github is now a native ES Module
  • Node 14 and 16 are no longer supported

v8.1.0

Compare Source

Features

v8.0.9

Compare Source

Bug Fixes

v8.0.8

Compare Source

Bug Fixes
  • Use Octokit for request retries and throttling to prevent rate limit errors (#​487) (3dc59ec)

v8.0.7

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (8bba5f0)

v8.0.6

Compare Source

Bug Fixes

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Bug Fixes
  • revert "fix(deps): update dependency url-join to v5" (6e4dfca)

v8.0.3

Compare Source

Bug Fixes
  • deps: update dependency url-join to v5 (7725391)

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Bug Fixes
  • deps: update dependency npm to v10 (819f257)
Features
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)
BREAKING CHANGES
  • node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

v10.0.6

Compare Source

Bug Fixes

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes

v10.0.3

Compare Source

Bug Fixes

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Bug Fixes
  • aggregate-error: upgraded to the latest version (7285e05)
  • deps: upgraded npm to v9 (2a79f80)
  • execa: upgraded to the latest version (7c74660)
  • normalize-url: upgraded to the latest version (b55bb01)
  • remove support for legacy auth (51ab3c8)
  • tempy: upgraded to the latest version of tempy (f1992a5)
Code Refactoring
  • esm: converted the package to esm (2d8ff15)
Features
  • node-versions: dropped support for node versions below v18 (aff3574)
  • semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)
BREAKING CHANGES
  • deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
    can be found at https://github.com/npm/cli/releases/tag/v9.0.0
  • semantic-release-peer: the required version of semantic-release has been
    raised to v20.1.0 in order to support loading of ESM plugins
  • aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
  • node-versions: node v18 is now the minimum required node version
  • esm: @semantic-release/npm is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare,
    publish, addChannel)

v9.0.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (7157d76)
  • deps: update dependency npm to v9 (28265ec)
  • deps: update dependency registry-auth-token to v5 (187671f)
  • revert): "fix(deps: update dependency npm to v9" (#​561) (c28a848)

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Bug Fixes
  • add preferLocal option to allow execa to use local npm version (#​445) (002439e)
  • updated the peer requirement for semantic-release to the new stable version (575a5a4)
  • updated the peer requirement on semantic-release to a version matching the engines definition of this package (2d1f5f2)
  • upgrade npm dependency to v8 (a12d6e5)
BREAKING CHANGES
  • the minimum required peer of semantic-release has been raised to match the engines.node requirements of this package
  • npm v8 dropped support for node v15, so it is no longer supported in this plugin. this should be low impact since node v15 is already EOL

Co-authored-by: Matt Travi programmer@travi.org

v8.0.3

Compare Source

Reverts

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

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

Co-authored-by: Matt Travi programmer@travi.org

semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.0.2

Compare Source

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

v13.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (5655b18)
  • node-versions: dropped support for node v18 and v19 (e65959a)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v12.1.0

[Compa


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, 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.

@changelogg
Copy link

changelogg bot commented Oct 19, 2021

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

@github-actions
Copy link

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

@github-actions
Copy link

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

@github-actions
Copy link

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@github-actions
Copy link

github-actions bot commented Oct 19, 2021

Mega-Linter status: ✅ SUCCESS

See errors details in artifact Mega-Linter reports on GitHub Action page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 410c43a to 723a5c3 Compare March 7, 2022 17:06
@viezly
Copy link

viezly bot commented Mar 7, 2022

Pull request by bot. No need to analyze

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 723a5c3 to ef6ee04 Compare April 25, 2022 00:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ef6ee04 to 6b2a770 Compare September 25, 2022 13:51
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Dependency Scan (nodejs) 5 11 7 0
Security Audit for Infrastructure 0 0 0 6

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6b2a770 to 9348cb3 Compare March 16, 2023 13:52
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Dependency Scan (universal) 1 7 3 0
Security Audit for Infrastructure 0 0 0 6

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9348cb3 to 131556e Compare March 24, 2023 20:15
@socket-security
Copy link

socket-security bot commented Mar 24, 2023

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Dependency Scan (universal) 1 8 3 0
Security Audit for Infrastructure 0 0 0 6

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 732af77 to bcef7e1 Compare June 2, 2023 22:33
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Dependency Scan (universal) 1 9 3 0
Security Audit for Infrastructure 0 0 0 6

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from b0bda93 to 9e1765b Compare June 9, 2023 21:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9e1765b to 5407b84 Compare July 4, 2023 19:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5407b84 to ae551f0 Compare July 16, 2023 03:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ae551f0 to 3207f72 Compare August 19, 2023 16:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7b516c6 to 3d01e82 Compare April 6, 2024 21:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 82735a9 to 06041a8 Compare May 16, 2024 05:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 06041a8 to 15220ac Compare May 22, 2024 19:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from a809218 to 1da4ebb Compare June 5, 2024 01:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1da4ebb to e185f34 Compare June 22, 2024 04:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e185f34 to 1987d86 Compare July 9, 2024 20:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ac92f94 to 5a24e8a Compare July 26, 2024 01:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 5f2efe5 to 5ed051a Compare August 15, 2024 20:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5ed051a to 7ddb109 Compare August 20, 2024 21:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7ddb109 to 9856a05 Compare September 2, 2024 16:46
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Security Audit for Infrastructure 0 0 0 6

Recommendation

Looks good ✔️

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9856a05 to fb41007 Compare September 2, 2024 18:40
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scan Summary

Tool Critical High Medium Low Status
Dependency Scan (universal) 0 7 2 0
Security Audit for Infrastructure 0 0 0 6

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from aa51fa3 to 1d1c6ba Compare September 6, 2024 01:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from eb1e5a0 to 7dec44e Compare September 20, 2024 18:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7dec44e to d55bdc7 Compare September 24, 2024 20:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d55bdc7 to e216a7d Compare November 6, 2024 19:48
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e216a7d to d64a7d6 Compare December 16, 2024 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants