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 semantic-release monorepo (major) #40

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 10, 2019

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 15.1.4 -> 24.2.1 age adoption passing confidence
travis-deploy-once 4.4.1 -> 5.0.11 age adoption passing confidence

Release Notes

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

v24.2.1

Compare Source

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

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.

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

v21.0.1

Compare Source

Bug Fixes

v21.0.0

Compare Source

BREAKING CHANGES
  • deps: the npm plugin has updated the npm dependency to v9
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
Bug Fixes
  • deps: bump @semantic-release/npm to ^10.0.0 (d647433)

v20.1.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v7.1.1 (c38b53a)

v20.1.2

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8.1.2 (fbede54)

v20.1.1

Compare Source

Bug Fixes

v20.1.0

Compare Source

Features

v20.0.4

Compare Source

Bug Fixes
  • windows: fixed issues preventing execution from windows (#​2672) (5df624c)

v20.0.3

Compare Source

Reverts

v20.0.2

Compare Source

Bug Fixes

v20.0.1

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8 (f914c1e)
  • deps: update dependency hosted-git-info to v6 (c4da008)

v20.0.0

Compare Source

BREAKING CHANGES
  • esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
  • esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
  • node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.
Features
Bug Fixes
  • env-ci: updated to the stable esm-only version (#​2632) (918eb59)
  • secrets-masking: used the proper named import from hook-std to enable masking for stderr (#​2619) (cf6befa)

v19.0.5

Compare Source

Reverts

v19.0.4

Compare Source

Bug Fixes

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

v18.0.1

Compare Source

Bug Fixes

v18.0.0

Compare Source

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

v17.4.7

Compare Source

Bug Fixes
  • engines: fixed defined node version to account for the higher requirement from the npm plugin (#​2088) (ea52e17)

v17.4.6

Compare Source

Bug Fixes

v17.4.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v3 (6e4beb8)

v17.4.4

Compare Source

Bug Fixes

v17.4.3

Compare Source

Bug Fixes
  • bump minimal version of lodash to address CVE-2021-23337 (#​1931) (55194c1)

v17.4.2

Compare Source

Bug Fixes

v17.4.1

Compare Source

Bug Fixes

v17.4.0

Compare Source

Features

v17.3.9

Compare Source

Bug Fixes

v17.3.8

Compare Source

Bug Fixes
  • deps: update dependency marked to v2 (a2eaed0)

v17.3.7

Compare Source

Bug Fixes

v17.3.6

Compare Source

Bug Fixes

v17.3.5

Compare Source

Bug Fixes

v17.3.4

Compare Source

Bug Fixes

v17.3.3

Compare Source

Bug Fixes

v17.3.2

Compare Source

Bug Fixes

v17.3.1

Compare Source

Bug Fixes

v17.3.0

Compare Source

Features

v17.2.4

Compare Source

Bug Fixes

v17.2.3

Compare Source

Bug Fixes
  • mask secrets when characters get uri encoded (ca90b34)

v17.2.2

Compare Source

Bug Fixes
  • don't parse port as part of the path in repository URLs (#​1671) (77a75f0)
  • use valid git credentials when multiple are provided (#​1669) (2bf3771)

v17.2.1

Compare Source

Reverts

v17.2.0

Compare Source

Features
  • throw an Error if package.json has duplicate "repository" key (#​1656) (b8fb35c)

v17.1.2

Compare Source

Bug Fixes

v17.1.1

Compare Source

Bug Fixes

v17.1.0

Compare Source

Features
  • bitbucket-basic-auth: support for bitbucket server basic auth (#​1578) (a465801)

v17.0.8

Compare Source

Bug Fixes
  • prevent false positive secret replacement for Golang projects (#​1562) (eed1d3c)

v17.0.7

Compare Source

Bug Fixes

v17.0.6

Compare Source

Bug Fixes

v17.0.5

Compare Source

Bug Fixes
  • adapt for semver to version 7.3.2 (0363790)

v17.0.4

Compare Source

Bug Fixes
  • add repositoryUrl in logs (55be0ba)

v17.0.3

Compare Source

Bug Fixes
  • pass a branch name to getGitAuthUrl (e7bede1)

v17.0.2

Compare Source

Bug Fixes
  • package: update marked-terminal to version 4.0.0 (8ce2d6e)

v17.0.1

Compare Source

Bug Fixes

v17.0.0

Compare Source

BREAKING CHANGES
  • Require Node.js >= 10.18

v16.0.4

Compare Source

Bug Fixes
  • correct error when remote repository has no branches (c6b1076)

v16.0.3

Compare Source

Bug Fixes
  • use --no-verify when testing the Git permissions (b54b20d)

v16.0.2

Compare Source

Bug Fixes
  • fetch tags on repo cached by the CI (6b5b02e)

v16.0.1

Compare Source

Bug Fixes
  • package: update env-ci to version 5.0.0 (3739ab5)

v16.0.0

Compare Source

BREAKING CHANGES
  • ⚠️ For v16.0.0@​beta users only:

    In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the @{channel} suffix is no longer necessary.

    The tags formatted as v{version}@​{channel} will now be ignored. If you have releases using this format you will have to upgrade them:

    • Find all the versions that have been released on a branch other than the default one by searching for all tags formatted as v{version}@​{channel}
    • For each of those version:
      • Create a tag without the {@​channel} if none doesn't already exists
      • Add a Git note to the tag without the {@​channel} containing the channels on which the version was released formatted as {"channels":["channel1","channel2"]} and using null for the default channel (for example.{"channels":[null,"channel1","channel2"]})
      • Push the tags and notes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9e792e1 to f224baa Compare January 18, 2020 13:53
@renovate renovate bot changed the title chore(deps): update dependency travis-deploy-once to v5 chore(deps): update semantic-release monorepo (major) Jan 18, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f224baa to 1426706 Compare February 8, 2020 12:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1426706 to c566073 Compare February 16, 2020 06:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c566073 to 10d219a Compare March 10, 2020 13:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 10d219a to 9ac6124 Compare April 26, 2020 08:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9ac6124 to eb801ef Compare June 30, 2020 12:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from eb801ef to 6af7a29 Compare October 25, 2020 17:58
@renovate renovate bot changed the title chore(deps): update semantic-release monorepo (major) chore(deps): update dependency travis-deploy-once to v5 Nov 24, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6af7a29 to 11997a4 Compare January 5, 2021 13:49
@renovate renovate bot changed the title chore(deps): update dependency travis-deploy-once to v5 chore(deps): update semantic-release monorepo (major) Jan 5, 2021
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 11997a4 to 692ea59 Compare January 24, 2021 15:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 692ea59 to f29087b Compare February 9, 2021 04:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f29087b to c0aa1e3 Compare April 26, 2021 15:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c0aa1e3 to cf6ed87 Compare May 15, 2021 19:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cf6ed87 to a9717d9 Compare October 19, 2021 01:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a9717d9 to 5b51271 Compare March 7, 2022 17:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5b51271 to 99c69e2 Compare June 18, 2022 23:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 99c69e2 to 18516d0 Compare September 25, 2022 13:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 18516d0 to 56f13c9 Compare March 17, 2023 02:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 56f13c9 to 58bc2df Compare March 24, 2023 23:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 79cf80c to 8c3f494 Compare June 3, 2023 05:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8c3f494 to 0f74600 Compare June 10, 2023 02:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d55ac1d to 8fb462f Compare July 5, 2023 02:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 089201f to 39eee4f Compare August 26, 2023 14:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 39eee4f to 584f82b Compare September 16, 2023 14:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 99061f4 to 0b6e0fc Compare September 23, 2023 08:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0b6e0fc to 07b424f Compare September 25, 2023 05:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from aeb95c7 to 8899d00 Compare November 4, 2023 02:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8899d00 to e438bc1 Compare November 17, 2023 14:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 1f6a093 to 6dd8dab Compare December 13, 2023 05:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6dd8dab to 43cb797 Compare January 13, 2024 08:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ee4f87b to 3ffd92b Compare February 8, 2024 01:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from a432b9f to 4b07d15 Compare March 19, 2024 02:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4b07d15 to eb78be9 Compare March 26, 2024 02:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8a05659 to 3d24dae Compare April 10, 2024 01:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3d24dae to 71aacf9 Compare May 11, 2024 05:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 71aacf9 to 7095639 Compare June 1, 2024 08:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7095639 to 4c3deca Compare August 17, 2024 17:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4c3deca to 7c7e736 Compare September 11, 2024 05:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7c7e736 to 90ae5f8 Compare September 28, 2024 05:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 90ae5f8 to 02abd1a Compare October 19, 2024 05:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 02abd1a to 8427ea4 Compare October 26, 2024 08:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8427ea4 to 2c0fc92 Compare January 4, 2025 14:39
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