Skip to content

chore(deps): update semantic-release monorepo (major)#290

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

chore(deps): update semantic-release monorepo (major)#290
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-semantic-release-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jan 9, 2020

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 3.0.66.0.3 age confidence
@semantic-release/git 7.0.1810.0.1 age confidence
@semantic-release/github 5.5.812.0.9 age confidence
@semantic-release/npm 5.3.513.1.5 age confidence

Release Notes

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

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

v5.0.1

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore
  • require Node.js >=10.18 (5ffdf49)
BREAKING CHANGES
  • Require Node.js >= 10.18

v4.0.0

Compare Source

Features
  • require Node.js >=10.13 (1f483af)
BREAKING CHANGES
  • Require Node.js >= 10.13
semantic-release/git (@​semantic-release/git)

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

v9.0.0

Compare Source

chore
  • require Node.js >=10.18 (4016fcc)
BREAKING CHANGES
  • Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (9c1dc67)
  • include deleted files in release commit (f59d20c)
  • package: update aggregate-error to version 2.0.0 (3eb8f60)
  • package: update execa to version 2.0.2 (9404d44)
  • package: update execa to version 3.0.0 (e6af5b4)
  • look for modified fiels to commit only if there files matching the globs (d97c030)
  • update globby to latest version (9e2b2e5)
Features
  • require Node.js >=10.13 (81955b8)
  • require Node.js >=8.15 (15356b1)
  • support branch parameter from semantic-release@​16.0.0 (02b1f6d)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15
semantic-release/github (@​semantic-release/github)

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

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

v8.1.0

Compare Source

Features

v8.0.9

Compare Source

Bug Fixes

v8.0.8

Compare Source

Bug Fixes
  • Use Octokit for request retries and throttling to prevent rate limit errors (#​487) (3dc59ec)

v8.0.7

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (8bba5f0)

v8.0.6

Compare Source

Bug Fixes

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Bug Fixes
  • revert "fix(deps): update dependency url-join to v5" (6e4dfca)

v8.0.3

Compare Source

Bug Fixes
  • deps: update dependency url-join to v5 (7725391)

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v7.2.3

Compare Source

Bug Fixes

v7.2.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (1a28625)

v7.2.1

Compare Source

Bug Fixes
  • allow proxy to be false and fallback an empty string (#​356) (bea917f)

v7.2.0

Compare Source

Features

v7.1.2

Compare Source

Bug Fixes

v7.1.1

Compare Source

Bug Fixes

v7.1.0

Compare Source

Features

v7.0.7

Compare Source

Bug Fixes
  • skip permission verification exception when Github Apps (#​272) (32654fb)

v7.0.6

Compare Source

Bug Fixes

v7.0.5

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (884dfee)

v7.0.4

Compare Source

Bug Fixes

v7.0.3

Compare Source

Bug Fixes
  • package: update https-proxy-agent to version 5.0.0 (3a5d3e4)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes
  • package: update globby to version 11.0.0 (e055e41)

v7.0.0

Compare Source

chore
  • require Node.js >=10.18 (fb249b7)
BREAKING CHANGES
  • Require Node.js >= 10.18

v6.0.2

Compare Source

Bug Fixes
  • package: update http-proxy-agent to version 4.0.0 (2a0a8f8)

v6.0.1

Compare Source

Bug Fixes
  • package: update issue-parser to version 6.0.0 (b02a35b)

v6.0.0

Compare Source

Bug Fixes
  • adapt for latest @​octokit/rest to remove deprecation warnings (#​177) (b2bc352)
  • use correct peerDependencies for semantic-release (742b521)
  • use the branch.main flag to determine is the release need the prerelease flag (7aaeb0f)
  • package: update @​octokit/rest to version 16.13.1 (4c756b2)
  • package: update aggregate-error to version 2.0.0 (7d6b7f0)
  • package: update aggregate-error to version 3.0.0 (2f08578)
  • package: update p-filter to version 2.0.0 (bab986f)
  • package: update p-retry to version 3.0.0 (36aab02)
  • package: update p-retry to version 4.0.0 (01822de)
  • also add comment/label to open issues (b69986f)
  • release debug messsage in publish (0a3ed26)
  • retrieve the branch name from context.branch (5f19284)
  • update globby to latest version (2b5e557)
  • update globby to latest version (c290940)
  • when adding labels, expect labels array to be sent in request body for GHE support (a81a825)
Features
  • add addChannel plugin step (589a5c4)
  • append assets before release (8eb8d66)
  • require Node.js >=10.13 (bd4322d)
  • support nextRelease.channel property in publish step (869c827)
BREAKING CHANGES
  • Require Node.js >= 10.13
semantic-release/npm (@​semantic-release/npm)

v13.1.5

Compare Source

Bug Fixes

v13.1.4

Compare Source

Bug Fixes

v13.1.3

Compare Source

Bug Fixes

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • publish-dry-run: temporarily remove the addition of dry-running the publish step (30bd176)

v13.1.0

Compare Source

Features
  • trusted-publishing: verify auth, considering OIDC vs tokens from various registries (e3319f1), closes #​958
  • trusted-publishing: refine the messages for related errors (316ce21), closes #​958
  • trusted-publishing: make request to verify if OIDC token exchange can succeed (c80ecb0), closes #​958
  • trusted-publishing: pass id-token as bearer header for github actions (d83b727), closes #​958
  • trusted-publishing: pass id-token as bearer header for gitlab pipelines (6d1c3cf), closes #​958
  • trusted-publishing: handle failure to retrieve id-token in the context of github actions (b673257), closes #​958
  • auth-error: update messaging for auth failure to be less token specific (e24967d)
  • auth: attempt a dry-run publish to determine auth status (841dc67)
Bug Fixes
  • trusted-publishing: uri encode the package name for the token exchange request (3dd95d0), closes #​958
  • auth: throw appropriate err

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

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

@commit-lint

commit-lint Bot commented Jan 9, 2020

Copy link
Copy Markdown

Chore

  • deps: update semantic-release monorepo (037895f)

Contributors

renovate[bot]

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

  • @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
  • @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
  • @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
  • @Commit-Lint merge disable will desactivate merge dependabot PR
  • @Commit-Lint review will approve dependabot PR
  • @Commit-Lint stop review will stop approve dependabot PR

@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 73ba018 to 27bcc22 Compare January 9, 2020 20:01
@renovate renovate Bot changed the title chore(deps): update dependency @semantic-release/git to v8 chore(deps): update semantic-release monorepo (major) Jan 9, 2020
@coveralls

coveralls commented Jan 9, 2020

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 75.0% when pulling 69d37ac on renovate/major-semantic-release-monorepo into b488095 on master.

@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from d6d6e55 to a36ca12 Compare January 15, 2020 18:51
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 9 times, most recently from 74bad9b to a8f8bf4 Compare January 28, 2020 16:40
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from c119d98 to 64f3730 Compare February 3, 2020 17:24
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from e167cfb to 2e5a5a1 Compare February 13, 2020 01:04
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 052ce2d to 9114ef3 Compare February 20, 2020 21:40
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 9114ef3 to e95c3a6 Compare March 1, 2020 14:50
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from e95c3a6 to 9b95a94 Compare March 9, 2020 15:34
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 9b95a94 to edd0dc2 Compare March 19, 2020 15:56
@renovate renovate Bot changed the title chore(deps): update semantic-release monorepo (major) chore(deps): update dependency semantic-release to v17 Aug 6, 2020
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to v17 chore(deps): update semantic-release monorepo (major) Aug 6, 2020
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 2c6a292 to f301d65 Compare September 7, 2020 20:37
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from f301d65 to fb10421 Compare September 17, 2020 19:33
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 99f5611 to 18e0c73 Compare October 11, 2020 22:08
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 18e0c73 to edcab62 Compare October 12, 2020 14:59
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from edcab62 to 8e43949 Compare October 29, 2020 21:42
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 8efb14b to 365f280 Compare November 17, 2020 18:26
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 365f280 to 0f01e95 Compare December 3, 2020 06:45
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 0f01e95 to 135f4c6 Compare January 17, 2021 20:13
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d4d4c20 to 0e70891 Compare April 5, 2021 15:33
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 0e70891 to 83e6d24 Compare April 8, 2021 16:53
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 83e6d24 to 69d37ac Compare May 9, 2021 23:43
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 69d37ac to 3b1acef Compare October 18, 2021 22:05
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 3b1acef to 6d826b9 Compare March 7, 2022 13:31
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 6d826b9 to 80d79fa Compare April 24, 2022 22:03
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 80d79fa to 4b11b48 Compare June 18, 2022 23:25
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 4b11b48 to 5876da0 Compare September 25, 2022 23:00
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 5876da0 to 514d47d Compare March 17, 2023 00:15
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 514d47d to c84157d Compare March 25, 2023 00:32
@renovate renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c84157d to bc3bc8a Compare April 17, 2023 10:12
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.

1 participant