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(dependencies): update dependency @semantic-release/exec to v7 #233

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 22, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/exec 5.0.0 -> 7.0.3 age adoption passing confidence

Release Notes

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

v7.0.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

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 (#​188) (020eab0)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

Configuration

📅 Schedule: Branch creation - "before 12pm on Wednesday" in timezone UTC, 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.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 870e2b8 to 7b503b2 Compare March 7, 2022 17:18
@codecov-commenter
Copy link

codecov-commenter commented Mar 7, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.89%. Comparing base (1385811) to head (ad93c00).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #233   +/-   ##
=======================================
  Coverage   78.89%   78.89%           
=======================================
  Files          22       22           
  Lines        1047     1047           
  Branches      240      240           
=======================================
  Hits          826      826           
  Misses        220      220           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7b503b2 to 98ce54b Compare September 25, 2022 16:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 98ce54b to be8558e Compare November 20, 2022 10:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from be8558e to e1f3177 Compare February 3, 2025 21:03
@renovate renovate bot changed the title chore(dependencies): update dependency @semantic-release/exec to v6 chore(dependencies): update dependency @semantic-release/exec to v7 Feb 3, 2025
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e1f3177 to e8dee6d Compare February 4, 2025 05:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e8dee6d to ad93c00 Compare February 6, 2025 04:34
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