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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency semantic-release to v17 [security] #29

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

chore(deps): update dependency semantic-release to v17 [security] #29

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 28, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 16.0.0-beta.18 -> 17.2.3 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2020-26226

Impact

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that become encoded when included in a URL.

Patches

Fixed in v17.2.3

Workarounds

Secrets that do not contain characters that become encoded when included in a URL are already masked properly.

Release Notes

semantic-release/semantic-release

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 version with multiple digits (9a04e64)
  • handle branch properties set to false (751a5f1)
  • harmonize parameters passed to getError (f96c660)
  • ignore lasst release only if pre-release on the same channel as current branch (990e85f)
  • increase next version on prerelease branch based on highest commit type (9ecc7a3)
  • look also for previous prerelease versions to determine the next one (9772563)
  • modify fetch function to handle CircleCI specifics (cbef9d1)
  • on maintenance branch add to channel only version >= to start range (c22ae17)
  • remove confusing logs when searching for releases to add to a channel (162b4b9)
  • remove hack to workaround GitHub Rebase & Merge (844e0b0)
  • remove unnecessary await (9a1af4d)
  • simplify get-tags algorithm (00420a8)
  • throws error if the commit associated with a tag cannot be found (1317348)
  • update plugin versions (0785a84)
  • update plugins dependencies (9890584)
  • verify is branch is up to date by comparing remote and local HEAD (a8747c4)
  • remove unnecessary branch parameter from push function (968b996)
  • revert to the correct refspec in fetch function (9948a74)
  • update plugins dependencies (73f0c77)
  • repositoryUrl: on beta repositoryUrl needs auth for pre-release flows (#​1186) (3610422)

v16.0.0-beta.47

Compare Source

Bug Fixes
  • correctly display command that errored out in logs (fc7205d)
Features
  • pass envi-ci values to plugins context (a8c747d)

v16.0.0-beta.46

Compare Source

Bug Fixes
  • look also for previous prerelease versions to determine the next one (9772563)

v16.0.0-beta.45

Compare Source

Bug Fixes
  • correct log when adding channel to tag (61665be)
  • remove unnecessary await (9a1af4d)
  • verify is branch is up to date by comparing remote and local HEAD (a8747c4)

v16.0.0-beta.44

Compare Source

Bug Fixes
  • increase next version on prerelease branch based on highest commit type (9ecc7a3)

v16.0.0-beta.43

Compare Source

Features
  • require Node.js >=10.13 (0716a45)
BREAKING CHANGES
  • Require Node.js >= 10.13

v16.0.0-beta.42

Compare Source

Features
  • allow to release any version on a branch if up to date with next branch (916c268)

v16.0.0-beta.41

Compare Source

Bug Fixes
  • package: update cosmiconfig to version 6.0.0 (ffff100)
  • package: update yargs to version 15.0.1 (2c13136)
  • use authenticated URL to check if local branch is up to date (7a939a8)

v16.0.0-beta.40

Compare Source

Bug Fixes
  • modify fetch function to handle CircleCI specifics (cbef9d1)

v16.0.0-beta.39

Compare Source

Features
  • use Git notes to store the channels on which a version has been released (b2c1b2c)
BREAKING CHANGES
  • this feature change the way semantic-release keep track of the channels on which a version has been released.
    It now use a JSON object stored in a Git note instead of Git tags formatted as v{version}@​{channel}.

The tags formatted as v{version}@​{channel} will now be ignored. If you have made releases with v16.0.0 on branches other than the default one you will have to update your repository.

The changes to make consist in:

  • Finding all the versions that have been released on a branch other than the default one by searching for all tags formatted v{version}@​{channel}
  • For each of those version:
    • Create a tag without the @​{channel} if none 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}

See this script to help with the migration: https://gist.github.com/pvdlg/6b19e529ee5c1a20645675a44e5b3239

v16.0.0-beta.38

Compare Source

Bug Fixes
  • add a flag indicate which branch is the main one (2caafba)

v16.0.0-beta.37

Compare Source

Bug Fixes
  • add channel to publish success log (5744c5e)
  • correctly determine release to add to a channel (aec96c7)
  • do not create tags in dry-run mode for released to add to a channel (97748c5)

v16.0.0-beta.36

Compare Source

Reverts
  • fix: update commit-analyzer dep version off errant publish (1275b8c)

v16.0.0-beta.35

Compare Source

Bug Fixes
  • update commit-analyzer dep version off errant publish (8d89105)

v16.0.0-beta.34

Compare Source

Bug Fixes
  • update plugins dependencies (9890584)

v16.0.0-beta.33

Compare Source

Bug Fixes
  • allow multiple branches with same channel (63f51ae)

v16.0.0-beta.32

Compare Source

Bug Fixes
  • handle branch properties set to false (751a5f1)

v16.0.0-beta.31

Compare Source

Bug Fixes
  • simplify get-tags algorithm (00420a8)

v16.0.0-beta.30

Compare Source

Bug Fixes
  • call getTagHead only when necessary (de77a79)
  • throws error if the commit associated with a tag cannot be found (1317348)

v16.0.0-beta.29

Compare Source

Bug Fixes
  • package: update micromatch to version 4.0.2 (5618641)

v16.0.0-beta.28

Compare Source

Bug Fixes
  • display erroring git commands properly (1edae67)
  • remove hack to workaround GitHub Rebase & Merge (844e0b0)
Performance Improvements
  • use git tag --merge <branch> to filter tags present in a branch history (cffe9a8)
BREAKING CHANGES
  • 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

v16.0.0-beta.27

Compare Source

Bug Fixes

v16.0.0-beta.26

Compare Source

Bug Fixes
  • package: update execa to version 3.0.0 (9537927)

v16.0.0-beta.25

Compare Source

Bug Fixes
  • update plugins dependencies (73f0c77)

v16.0.0-beta.24

Compare Source

Bug Fixes
  • allow to set ci option via API and config file (862ec4c)
  • correctly handle skipped releases (1243f79)
  • prefix git auth with "x-access-token:" when run in a GitHub Action (038e640)
  • package: update semver to version 6.0.0 (d61e3bc)
  • remove unnecessary branch parameter from push function (ffe1062)
  • package: update aggregate-error to version 2.0.0 (1aefd98)
  • package: update aggregate-error to version 3.0.0 (06fe435)
  • package: update dependency lodash to address security warnings (#​1253) (9a8a36c)
  • package: update env-ci to version 4.0.0 (8051294)
  • package: update execa to version 2.0.0 (52c48be)
  • package: update figures to version 3.0.0 (f4cf7c8)
  • package: update get-stream to version 5.0.0 (0a584de)
  • package: update hook-std to version 2.0.0 (db3fc3e)
  • package: update hosted-git-info to version 3.0.0 (391af98)
  • package: update marked to version 0.6.0 (b7aeaba)
  • package: update marked to version 0.7.0 (75f0830)
  • package: update p-locate to version 4.0.0 (a5babc6)
  • package: update p-reduce to version 2.0.0 (30723c5)
  • package: update read-pkg-up to version 5.0.0 (a90a103)
  • package: update read-pkg-up to version 6.0.0 (74103ab)
  • package: update resolve-from to version 5.0.0 (6f3c21a)
  • package: update yargs to version 13.1.0 (aed4ea2)
  • package: update yargs to version 14.0.0 (3c2fe35)
Features
  • allow publish plugins to return false in order to signify no release was done (70c68ef)
  • require Node.js >=8.15 (f1d983d)
Reverts
  • docs: broken link docs/03-recipes/travis.md (eea5de2)
  • docs: cleaned "Developer guide" section navigation (3c4a0fb)
  • docs: corrections and further clarifications (ce3d1bc)
  • docs: made doc file org clearer and augmented content (5e41dc8)
  • docs: note publishing on distribution channels in beta (54d8e3f)
  • docs: repared broken links to "CI configuration recipes" (e00b6c8)
  • docs: synched README.md and SUMMARY.md (e770c50)
  • docs: update semantic-release-cli broken link (58aaf05)
  • docs(contributing): added instructions on how to run gitbook locally (55c3616)
  • docs(contributing): copy/pasted "Use gitbook locally" instruction from original url (c517c70)
  • docs(recipes): cleaned doc and navigation (a6188d3)
  • feat: create annotated tags (0629f3c)
  • fix: prefix git auth url with "x-access-token:" when run in a GitHub Action (f67a667)
  • fix: revert to execa ^1.0.0 (fa62d0b)
  • fix(package): update @​semantic-release/github back to a build from the beta branch (d120eae)
BREAKING CHANGES
  • Require Node.js => 8.15

v16.0.0-beta.23

Compare Source

Bug Fixes

v16.0.0-beta.22

Compare Source

Features

v16.0.0-beta.21

Compare Source

Bug Fixes
  • revert to the correct refspec in fetch function (9948a74)

v16.0.0-beta.20

Compare Source

Bug Fixes
  • Add helpful detail to ERELEASEBRANCHES error message (#​1188) (37bcc9e)
  • repositoryUrl: on beta repositoryUrl needs auth for pre-release flows (#​1186) (3610422)

v16.0.0-beta.19

Compare Source

Bug Fixes
  • fix maintenance branch regex (a022996)

Renovate configuration

📅 Schedule: "" (UTC).

🚦 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 has been generated by WhiteSource Renovate. View repository job log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@renovate-bot