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(deps): update semantic-release monorepo (major) #869

Merged
merged 1 commit into from Jan 30, 2020

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 9, 2020

This PR contains the following updates:

Package Type Update Change
@semantic-release/changelog devDependencies major 3.0.6 -> 5.0.0
@semantic-release/git devDependencies major 7.0.18 -> 9.0.0
@semantic-release/npm devDependencies major 5.3.5 -> 7.0.0
semantic-release devDependencies major 15.14.0 -> 17.0.1

Release Notes

semantic-release/changelog

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

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/npm

v7.0.0

Compare Source

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

v6.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (d97dee5)
  • package: update semver to version 6.3.0 (c515862)
  • add dist-tag to publish and add-channel logs (db6ccd2)
  • use correct peerDependencies for semantic-release (8b47e7b)
  • package: pin npm to 6.5.0 (ddab7b7)
  • package: update aggregate-error to version 2.0.0 (df53298)
  • package: update aggregate-error to version 3.0.0 (3e0d5d0)
  • package: update execa to version 3.0.0 (b1780c1)
  • package: update npm to version 6.8.0 (2b0492e)
  • package: update read-pkg to version 5.0.0 (877ce40)
  • package: update vulnerable dependencies (#​185) (a96c6da)
  • skip tarball move if config is cwd (a224497)
  • package: update execa to version 2.0.2 (d2932ba)
  • package: update registry-auth-token to version 4.0.0 (2868b2c)
  • add dist-tag to publish log (2de37a1)
  • Honor NPM_CONFIG_USERCONFIG setting (932ea5e)
  • package: update fs-extra to version 8.0.0 (bf603e5)
  • return false if the npm publish is skipped (4a41228)
  • return false in addChannel if package is not published on npm (5434bab)
Features
  • add addChannel plugin step (fb96126)
  • require Node.js >=10.13 (6426458)
  • require Node.js >=8.15 (4caf538)
  • support nextRelease.channel property in publish step (b8deba7)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Node.js => 8.15
semantic-release/semantic-release

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)

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

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

@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
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from fa76115 to 3952f57 Compare January 15, 2020 18:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 04da65d to 3181edd Compare January 27, 2020 22:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3181edd to 610d51c Compare January 28, 2020 16:40
@xobotyi xobotyi merged commit 953714f into master Jan 30, 2020
@xobotyi xobotyi deleted the renovate/major-semantic-release-monorepo branch January 30, 2020 10:58
@streamich
Copy link
Owner

🎉 This PR is included in version 13.22.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants