Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Oct 18, 2021 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog ^5.0.1 → ^7.0.0 age confidence
@semantic-release/commit-analyzer ^8.0.1 → ^13.0.1 age confidence
@semantic-release/git ^9.0.0 → ^11.0.1 age confidence
@semantic-release/github ^7.2.0 → ^12.0.11 age confidence
@semantic-release/npm ^7.0.10 → ^13.2.0 age confidence
@semantic-release/release-notes-generator ^9.0.1 → ^14.1.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/changelog is now a native ES
    Module. It has named exports for each plugin hook (verifyConditions,
    prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/changelog is now
    v20.1.0
Other Notable Changes
  • Replaced xo with prettier with default configuration; following
    newly established convention
  • Replaced nyc with c8 for code coverage
  • Replaced lodash with lodash-es for proper esm support
Related Issue

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.1

Compare Source

Bug Fixes

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)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/git is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/git is now v20.1.0

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)

v12.0.11

Compare Source

Bug Fixes

v12.0.10

Compare Source

Bug Fixes

v12.0.9

Compare Source

Bug Fixes
  • asset-upload: stop setting content-length header manually (241f966), closes #​1224
  • local-undici: always use the locally installed undici instead of the node built-in version (40973e3), closes #​1224
  • publish: handle content-length header properly for asset uploads (#​1260) (28e3741), closes #​1224 #​1224

v12.0.8

Compare Source

Bug Fixes

v12.0.7

Compare Source

Bug Fixes

v12.0.6

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release PATCH request during publish (#​1169) (f516337)

v12.0.5

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release POST request during publish (#​1157) (38051ba)

v12.0.4

Compare Source

Bug Fixes

v12.0.3

Compare Source

Bug Fixes
  • extend GraphQL alias prefix to prevent hash collisions (#​1134) (ea6386d)

v12.0.2

Compare Source

Bug Fixes
  • add undici ProxyAgent support for GitHub Enterprise Server behind proxies (#​1104) (15def77)

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

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

Bug Fixes
  • glob-assets: remove unnecessary option when invoking globby() (#​924) (efe9f49)

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

Bug Fixes
  • edge-case: fetching associatedPRs on 100+ context.commits in success lifecycle (#​892) (dfe47e9)

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

Bug Fixes

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

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Moscow)

  • Branch creation
    • "after 10pm every weekday,before 5am every weekday,every weekend"
  • 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.

@changelogg

changelogg Bot commented Oct 18, 2021

Copy link
Copy Markdown

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

@auto-assign
auto-assign Bot requested a review from AlexRogalskiy October 18, 2021 20:58
@github-actions

Copy link
Copy Markdown

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
Copy Markdown

🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/major-semantic-release-monorepo

@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 93fa578 to 7dac948 Compare March 7, 2022 14:09
@viezly

viezly Bot commented Mar 7, 2022

Copy link
Copy Markdown

Pull request by bot. No need to analyze

@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 7dac948 to 8d6d8d1 Compare April 24, 2022 23:37
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 8d6d8d1 to eede372 Compare June 23, 2022 21:38
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from eede372 to 6406a58 Compare September 25, 2022 11:41
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 6406a58 to 771ba47 Compare March 17, 2023 08:21
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 771ba47 to d2eea18 Compare April 3, 2023 15:21
@socket-security

socket-security Bot commented Apr 3, 2023 •

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @pnpm/network.ca-file is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@13.1.5 → npm/@pnpm/network.ca-file@1.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@pnpm/network.ca-file@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm execa is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@13.1.5 → npm/execa@9.6.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/execa@9.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm npm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@13.1.5 → npm/npm@11.18.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm npm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/@semantic-release/npm@13.1.5 → npm/npm@11.18.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from d2eea18 to 7e19e82 Compare April 17, 2023 11:53
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 058fd90 to 7fa2467 Compare June 3, 2023 21:55
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 84fbb71 to b1e433d Compare June 9, 2023 22:02
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from b1e433d to f3c6b0d Compare July 4, 2023 17:16
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from f3c6b0d to 2b39a4b Compare July 16, 2023 03:31
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 2b39a4b to 4f282ae Compare August 19, 2023 17:04
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 0777c18 to 49f5964 Compare August 28, 2023 21:52
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 4ba181a to 97df497 Compare March 18, 2024 04:30
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 97df497 to 51e2ed0 Compare March 24, 2024 06:12
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 51e2ed0 to f48bcff Compare April 6, 2024 22:03
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 562a7b3 to 6bfbc9e Compare May 16, 2024 00:08
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 6bfbc9e to 0c9eb53 Compare May 22, 2024 19:00
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0280e1e to aca2791 Compare June 5, 2024 02:00
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from aca2791 to f715bbe Compare June 22, 2024 04:41
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0454eee to 810c1c7 Compare July 8, 2024 16:38
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from f7c65b9 to fc9113c Compare July 26, 2024 01:47
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ae7a734 to c167502 Compare August 15, 2024 19:07
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c167502 to 4779544 Compare August 20, 2024 22:21
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 8a8a0bd to 24f2333 Compare September 6, 2024 02:08
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ea065a3 to 76c0c01 Compare September 20, 2024 19:07
@github-actions

Copy link
Copy Markdown

Welcome, new contributor!

@socket-security

socket-security Bot commented Jul 21, 2026 •

Copy link
Copy Markdown

All alerts resolved. 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

@socket-security

socket-security Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

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