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) #80

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 17, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 15.14.0 -> 24.0.0 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.0.0

Compare Source

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
      • Update the GitHub releases that refer to a tag formatted as v{version}@​{channel} to use the tag without it
      • Delete the tags formatted as v{version}@​{channel}
  • Require Node.js >= 10.13

  • Git CLI version 2.7.1 or higher is now required: The --merge option of the git tag command has been added in Git version 2.7.1 and is now used by semantic-release

  • Regexp are not supported anymore for property matching in the releaseRules option.

    Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.

  • The branch option has been removed in favor of branches

  • The new branches option expect either an Array or a single branch definition. To migrate your configuration:

    • If you want to publish package from multiple branches, please see the configuration documentation
    • If you use the default configuration and want to publish only from master: nothing to change
    • If you use the branch configuration and want to publish only from one branch: replace branch with branches ("branch": "my-release-branch" => "branches": "my-release-branch")
Features
  • allow addChannel plugins to return false in order to signify no release was done (e1c7269)
  • allow publish plugins to return false in order to signify no release was done (47484f5)
  • allow to release any version on a branch if up to date with next branch (916c268)
  • support multiple branches and distribution channels (7b40524)
  • use Git notes to store the channels on which a version has been released (b2c1b2c)
  • package: update @​semantic-release/commit-analyzer to version 7.0.0 (e63e753)
Performance Improvements
  • use git tag --merge <branch> to filter tags present in a branch history (cffe9a8)
Bug Fixes
  • add channel to publish success log (5744c5e)
  • add a flag indicate which branch is the main one (2caafba)
  • Add helpful detail to ERELEASEBRANCHES error message (#​1188) (37bcc9e)
  • allow multiple branches with same channel (63f51ae)
  • allow to set ci option via API and config file (2faff26)
  • call getTagHead only when necessary (de77a79)
  • call success plugin only once for releases added to a channel (9a023b4)
  • correct log when adding channel to tag (61665be)
  • correctly determine next pre-release version (0457a07)
  • correctly determine release to add to a channel (aec96c7)
  • correctly handle skipped releases (89663d3)
  • display erroring git commands properly (1edae67)
  • do not call addChannelfor 2 merged branches configured with the same channel (4aad9cd)
  • do not create tags in dry-run mode for released to add to a channel (97748c5)
  • fetch all release branches on CI (b729183)
  • fix branch type regexp to handle version with multiple digits (52ca0b3)
  • fix maintenance branch regex (a022996)
  • fix range regexp to handle ve

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 Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d02be1d to ccaa234 Compare September 7, 2019 11:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ccaa234 to d2babb8 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 d2babb8 to 8e08356 Compare February 8, 2020 12:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8e08356 to 220fb80 Compare February 16, 2020 05:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 220fb80 to bb2f97a Compare March 10, 2020 13:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bb2f97a to a3576f1 Compare April 26, 2020 08:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a3576f1 to e584415 Compare June 30, 2020 12:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e584415 to 387ff6f Compare October 25, 2020 17:57
@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 387ff6f to 63f3d20 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 63f3d20 to b78eb03 Compare January 24, 2021 19:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d020aef to 1f1cb3b Compare February 12, 2021 23:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from da5d895 to 10d6128 Compare March 3, 2021 21:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 10d6128 to fdca905 Compare April 26, 2021 13:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fdca905 to c828756 Compare May 15, 2021 19:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c828756 to c0f2386 Compare October 18, 2021 18:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c0f2386 to 16c825e Compare March 7, 2022 12:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 16c825e to 3e832fb Compare June 18, 2022 23:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3e832fb to f01a081 Compare September 25, 2022 15:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f01a081 to 5cb10b8 Compare November 20, 2022 14:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5cb10b8 to 36f3527 Compare March 17, 2023 06:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 36f3527 to 37668d2 Compare March 24, 2023 23:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 37668d2 to a0fdc4c Compare April 3, 2023 10:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c6d8e9b to 25d8f7f Compare June 2, 2023 21:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 25d8f7f to 5d169db Compare June 9, 2023 23:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b042b22 to 485c1cd Compare July 5, 2023 03:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from c2a0269 to c9b1e07 Compare August 24, 2023 18:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 059f9fd to 581385a Compare September 23, 2023 00:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 581385a to 756a2c5 Compare September 24, 2023 18:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 7a94e46 to 7efbbba Compare November 3, 2023 21:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7efbbba to 5e7edc8 Compare November 17, 2023 03:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 328c33b to 8b34d91 Compare December 12, 2023 04:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8b34d91 to 622a934 Compare December 12, 2023 07:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 622a934 to 76af6fe Compare January 12, 2024 22:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 7794df8 to 8511762 Compare February 7, 2024 16:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from e0a3217 to acd04d9 Compare March 18, 2024 14:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from acd04d9 to 0a82e78 Compare March 24, 2024 18:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 874ac77 to 6b62c83 Compare April 9, 2024 22:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from addb05a to 0c71900 Compare May 10, 2024 23:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0c71900 to 9caaaf9 Compare May 31, 2024 23:45
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.

None yet

0 participants