fix(deps): update dependency semantic-release to v15 - abandoned by renovate[bot] · Pull Request #8 · jcoreio/defaultenv

package: update git-url-parse to version 9.0.0 (7c9ec41)
add trailing .git to repositoryUrl only if it's present in the configured URL (cb1f80c)

`v15.1.6`

Compare Source

Bug Fixes

match tag to tagFormat from the begining of the string (31ad231)

`v15.1.5`

Compare Source

Bug Fixes

package: update git-url-parse to version 8.3.1 (02746aa)

`v15.1.4`

Compare Source

Bug Fixes

handle case with no last release in history (51e340f)

`v15.1.3`

Compare Source

Bug Fixes

prevent git prompt before permissions verification (30ee231)
remove execa timeout (3c46455)

`v15.1.2`

Compare Source

Bug Fixes

prevent git CLI to prompt user/password on CI (7c48afa)

`v15.1.1`

Compare Source

Bug Fixes

package: Remove commander.js dependency (#704) (c84ac15)

`v15.1.0`

Compare Source

Features

allow to use shorthand for repositoryUrl (5f1d530)

`v15.0.4`

Compare Source

Bug Fixes

package: update execa to version 0.10.0 (f13ec6a)

`v15.0.3`

Compare Source

Bug Fixes

convert git+https URL in package.json to https (b0b4fc8)
use correct debug namespace (6f74dcb)

`v15.0.2`

Compare Source

Bug Fixes

exclude prereleases from version retrived by getLastRelease (e4618a2)

`v15.0.1`

Compare Source

Bug Fixes

remove unecessary console.log (e5a73d8)

`v15.0.0`

Compare Source

Features

add the prepare plugin hook (c2beb64)

BREAKING CHANGES

Committing or creating files in the publish plugin hook is not supported anymore and now must be done in the prepare hook

Plugins with a publish hook that makes a commit or create a file that can be committed must use the prepare hook.

`v14.0.4`

Compare Source

Bug Fixes

exclude empty env var value from replacement (20246c0)

`v14.0.3`

Compare Source

Bug Fixes

allow boolean option to be set in config file (857d418)

`v14.0.2`

Compare Source

Bug Fixes

verify branch first (1966f0e)

`v14.0.1`

Compare Source

Bug Fixes

do not transform repositoryUrl if it allow to push (305f4ee)

`v14.0.0`

Compare Source

Features

use @semantic-release as default for success and fail hooks (9788fca)

BREAKING CHANGES

success and fail hooks are now enabled by default

In order to disable the @semantic-release/github plugin for the success and fail hook, the corresponding options have to be set to false in the semantic-release configuration:

{
  "release": {
    "success": false,
    "fail": false
  }
}

Users who do not use the @semantic-release/github plugin, should disable it in the success and fail by setting the corresponding options to false or to alternative plugin providing success and fail hooks.

Migration Guide

For non GitHub users

If you do no want the success and fail notification on GitHub or if you are not using GitHub you need to disable the success and fail plugin hooks by adding the following to your semantic-release configuration:

Add the following to your semantic-release configuration:

{
  "release": {
    "success": false,
    "fail": false
  }
}

For GitHub users

GitHub users do not need to change anything. You will get comments on PR and issues when a release that resolved them is publish as well as an issue when a problem happen that prevent to perform a release.

`v13.4.1`

Compare Source

Bug Fixes

remove the github plugin from default success and fail hooks (04f3061)

`v13.4.0`

Compare Source
⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Bug Fixes

log current version of semantic-release (f92677b)
set repository authentication when repositoryUrl is set as an option (ce1e74f)

Features

improve CLI (97cb354)

`v13.3.1`

Compare Source
⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Bug Fixes

fix EPLUGINCONF error details (9dd127b)

`v13.3.0`

Compare Source
⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Features

add success and fail notification plugins (49f5e70)
allow plugins to throw an iterable list of errors (9b2f6bf)

`v13.2.0`

Compare Source

Features

add debug logs for git commands (687435b)

`v13.1.5`

Compare Source

Bug Fixes

debug log all options (7e785fa)

`v13.1.4`

Compare Source

Bug Fixes

package: update git-url-parse to version 8.1.0 (2edd9da)

`v13.1.3`

Compare Source

Bug Fixes

always transform git+https url to https (cbf5785)

`v13.1.2`

Compare Source

Bug Fixes

package: update [@semantic-release]/github to version 4.0.2 (af8c830)

`v13.1.1`

Compare Source

Bug Fixes

use long option to delete tag in git push (d820823)

`v13.1.0`

Compare Source

Bug Fixes

log all core verification errors (faabffb)

Features

add tagFormat option to customize Git tag name (39536fa)

`v13.0.2`

Compare Source

Bug Fixes

prioritize GIT_CREDENTIALS for gtit credentials (467635b)

`v13.0.1`

Compare Source

Bug Fixes

hide sensitive info for Buffer and undefined (8b3605d)

`v13.0.0`

Compare Source

Bug Fixes

rename the --repositoryUrl CLI option to --repository-url (cb36dd4)

Features

get last release with git tags (d0b304e)

BREAKING CHANGES

The --repositoryUrl CLI options is replaced by --repository-url
Remove the getLastRelease plugin type

The getLastRelease plugins will not be called anymore.

Git repository authentication is now mandatory

The Git authentication is now mandatory and must be set via GH_TOKEN, GITHUB_TOKEN, GL_TOKEN, GITLAB_TOKEN or GIT_CREDENTIALS as described in CI configuration.

Migration Guide

Make sure the commit associated with the last release is tagged with `v<last_release_version>`

This will already be the case for all semantic-release users using the GitHub (default), Git or GitLab plugins or for any release done manually with npm publish.

Make sure the Git authentication is configured

This will already be the case for all semantic-release users using the GitHub (default), Git or GitLab plugins. See CI configuration.

This PR has been generated by Renovate Bot.

codecov · 2018-03-07T21:10:27Z

Codecov Report

Merging #8 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   96.92%   96.92%           
=======================================
  Files           1        1           
  Lines          65       65           
=======================================
  Hits           63       63           
  Misses          2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0865356...ad5cea5. Read the comment docs.

renovate · 2026-02-03T22:36:41Z

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

fix(deps): update dependency semantic-release to ^15.0.0

ad5cea5

renovate bot changed the title ~~fix(deps): update dependency semantic-release to ^15.0.0~~ fix(deps): update dependency semantic-release to v15 Apr 17, 2018

renovate bot changed the title ~~fix(deps): update dependency semantic-release to v15~~ Update dependency semantic-release to v15 May 9, 2018

renovate bot changed the title ~~Update dependency semantic-release to v15~~ fix(deps): update dependency semantic-release to v15 May 9, 2018

renovate bot changed the title ~~fix(deps): update dependency semantic-release to v15~~ fix(deps): update dependency semantic-release to v15 - abandoned Feb 3, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency semantic-release to v15 - abandoned#8

fix(deps): update dependency semantic-release to v15 - abandoned#8
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/semantic-release-15.x

renovate bot commented Mar 7, 2018 •

edited

Loading

Uh oh!

codecov bot commented Mar 7, 2018 •

edited

Loading

Uh oh!

renovate bot commented Feb 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate bot commented Mar 7, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Features

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Migration Guide

For non GitHub users

For GitHub users

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Migration Guide

Make sure the commit associated with the last release is tagged with v<last_release_version>

Make sure the Git authentication is configured

Uh oh!

codecov bot commented Mar 7, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

renovate bot commented Feb 3, 2026

Autoclosing Skipped

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Mar 7, 2018 •

edited

Loading

Make sure the commit associated with the last release is tagged with `v<last_release_version>`

codecov bot commented Mar 7, 2018 •

edited

Loading