Skip to content

chore: bump semantic-release and @semantic-release/git#19

Merged
raduachim merged 1 commit intomasterfrom
dependabot/npm_and_yarn/semantic-release-and-semantic-release/git-16.0.2
Jan 16, 2020
Merged

chore: bump semantic-release and @semantic-release/git#19
raduachim merged 1 commit intomasterfrom
dependabot/npm_and_yarn/semantic-release-and-semantic-release/git-16.0.2

Conversation

@dependabot-preview
Copy link
Copy Markdown
Contributor

Bumps semantic-release and @semantic-release/git. These dependencies needed to be updated together.
Updates semantic-release from 15.14.0 to 16.0.2

Release notes

Sourced from semantic-release's releases.

v16.0.2

16.0.2 (2020-01-15)

Bug Fixes

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

v16.0.1

16.0.1 (2020-01-10)

Bug Fixes

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

v16.0.0

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)
... (truncated)
Commits
  • 6b5b02e fix: fetch tags on repo cached by the CI
  • 28b5480 docs: correct plugin execution order
  • 3739ab5 fix(package): update env-ci to version 5.0.0
  • 11665b2 chore(package): update dependencies
  • 0785a84 fix: update plugin versions
  • 152bf45 Merge remote-tracking branch 'origin/beta'
  • 3ba8f2a Merge remote-tracking branch 'origin/master' into beta
  • 9772563 fix: look also for previous prerelease versions to determine the next one
  • 61665be fix: correct log when adding channel to tag
  • a8747c4 fix: verify is branch is up to date by comparing remote and local HEAD
  • Additional commits viewable in compare view

Updates @semantic-release/git from 7.0.18 to 8.0.0

Release notes

Sourced from @semantic-release/git's releases.

v8.0.0

8.0.0 (2020-01-09)

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

v7.1.0-beta.11

7.1.0-beta.11 (2019-12-19)

Bug Fixes

  • package: update execa to version 4.0.0 (9c1dc67)

v7.1.0-beta.10

7.1.0-beta.10 (2019-12-05)

Features

  • require Node.js >=10.13 (81955b8)

BREAKING CHANGES

  • Require Node.js >= 10.13

v7.1.0-beta.9

... (truncated)
Commits
  • 1fd1243 Merge remote-tracking branch 'origin/beta'
  • e312747 Merge remote-tracking branch 'origin/master' into beta
  • ceb9cca chore(package): update nyc to version 15.0.0
  • 3c70c90 chore(package): update sinon to version 8.0.0
  • 9c1dc67 fix(package): update execa to version 4.0.0
  • 6280bfd docs: recommend to use git merge --no-ff
  • 81955b8 feat: require Node.js >=10.13
  • 03237d7 Merge branch 'master' into beta
  • 16edc0b style: prettier formatting
  • f59d20c fix: include deleted files in release commit
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [semantic-release](https://github.com/semantic-release/semantic-release) and [@semantic-release/git](https://github.com/semantic-release/git). These dependencies needed to be updated together.

Updates `semantic-release` from 15.14.0 to 16.0.2
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v15.14.0...v16.0.2)

Updates `@semantic-release/git` from 7.0.18 to 8.0.0
- [Release notes](https://github.com/semantic-release/git/releases)
- [Commits](semantic-release/git@v7.0.18...v8.0.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview Bot added the dependencies Pull requests that update a dependency file label Jan 16, 2020
@raduachim raduachim merged commit c4344af into master Jan 16, 2020
@raduachim raduachim deleted the dependabot/npm_and_yarn/semantic-release-and-semantic-release/git-16.0.2 branch January 16, 2020 14:41
@ghost
Copy link
Copy Markdown

ghost commented Jan 16, 2020

🎉 This PR is included in version 0.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ghost ghost added the released label Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant