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

fix(deps): update semantic-release monorepo (major) #125

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

Conversation

slauger
Copy link
Owner

@slauger slauger commented Jun 5, 2023

This PR contains the following updates:

Package Type Update Change
@semantic-release/github dependencies major ^8.0.5 -> ^10.0.0
semantic-release dependencies major 21.0.1 -> 24.0.0

Release Notes

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

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

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
semantic-release/semantic-release (semantic-release)

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

Bug Fixes

v23.1.0

Compare Source

Features

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

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

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.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

v21.0.6

Compare Source

Bug Fixes
  • get correct version if prerelease branch shares version with ... (#​2416) (e4229f9)

v21.0.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v5 (452e1fa)

v21.0.4

Compare Source

Bug Fixes

v21.0.3

Compare Source

Bug Fixes
  • bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
  • bump @semantic-release/github to 9.0.0-beta.2 (#​2818) (6f19d77)
  • deps: updated the beta plugins to stable versions (3941018)

v21.0.2

Compare Source

Bug Fixes

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 Renovate Bot.

@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from b20d1a6 to 215eb25 Compare September 18, 2023 11:00
@slauger slauger changed the title fix(deps): update npm dependency @semantic-release/github to v9 fix(deps): update semantic-release monorepo (major) Sep 18, 2023
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 918977c to d418b3a Compare September 25, 2023 10:58
@slauger
Copy link
Owner Author

slauger commented Oct 17, 2023

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.

@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8c0d974 to 85370c7 Compare November 6, 2023 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from 85370c7 to 80532d6 Compare November 17, 2023 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ba14a97 to 1c2724c Compare December 6, 2023 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from 1c2724c to a4408f1 Compare December 12, 2023 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from a4408f1 to ce8cc55 Compare January 15, 2024 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 535227b to ddd7bee Compare February 8, 2024 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 9ec4cb2 to 95aa3a9 Compare March 19, 2024 10:57
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from 95aa3a9 to b48852d Compare March 25, 2024 10:57
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 600be96 to c742241 Compare April 10, 2024 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from c742241 to bed5395 Compare May 13, 2024 10:58
@slauger slauger force-pushed the renovate/major-semantic-release-monorepo branch from bed5395 to 70c7d3f Compare June 3, 2024 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants