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 dependency semantic-release to v24 #55

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 21.1.2 -> 24.1.1 age adoption passing confidence

Release Notes

semantic-release/semantic-release (semantic-release)

v24.1.1

Compare Source

v24.1.0

Compare Source

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • 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. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@socket-security
Copy link

socket-security bot commented Sep 17, 2023

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] environment, network Transitive: eval, filesystem, shell, unsafe +244 34.6 MB semantic-release-bot

🚮 Removed packages: npm/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 4 times, most recently from 93ea9d5 to d72d5d8 Compare September 25, 2023 17:44
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from f867b43 to 6aff00f Compare November 4, 2023 21:09
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 6aff00f to 2b4af80 Compare November 18, 2023 04:51
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 9b6ef6f to fa971e3 Compare December 13, 2023 01:00
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from fa971e3 to 88d7c49 Compare December 13, 2023 07:30
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 88d7c49 to 79e1d2c Compare January 13, 2024 22:07
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 13, 2024
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from f90d920 to f0fe63b Compare February 8, 2024 15:31
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 4317b19 to 4ecb7c0 Compare March 19, 2024 16:12
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 4ecb7c0 to 2f66cd5 Compare March 25, 2024 16:05
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 4eafbe8 to 8f5db51 Compare April 10, 2024 21:36
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 10a6fee to 8f6c8cf Compare May 11, 2024 23:09
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 8f6c8cf to 2894ef8 Compare June 2, 2024 00:50
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 Jun 2, 2024
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 2894ef8 to 9e0931e Compare August 18, 2024 14:11
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 9e0931e to c9d54f4 Compare September 12, 2024 06:39
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Obfuscated code npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

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

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

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