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 devdependencies #129

Merged
merged 1 commit into from
Jun 20, 2020
Merged

chore(deps): update devdependencies #129

merged 1 commit into from
Jun 20, 2020

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 20, 2020

This PR contains the following updates:

Package Type Update Change
@babel/core (source) devDependencies patch 7.10.2 -> 7.10.3
@types/react devDependencies patch 16.9.36 -> 16.9.38
@typescript-eslint/eslint-plugin devDependencies minor 3.2.0 -> 3.3.0
@typescript-eslint/parser devDependencies minor 3.2.0 -> 3.3.0
eslint (source) devDependencies minor 7.2.0 -> 7.3.0
eslint-plugin-prettier devDependencies patch 3.1.3 -> 3.1.4
lint-staged devDependencies patch 10.2.10 -> 10.2.11
shipjs devDependencies minor 0.19.0 -> 0.20.0
terser-webpack-plugin devDependencies patch 3.0.4 -> 3.0.6
webpack-cli devDependencies patch 3.3.11 -> 3.3.12

Release Notes

babel/babel

v7.10.3

Compare Source

v7.10.3 (2020-06-19)

Thanks @​AjayPoshak, @​jessethomson, @​sajadtorkamani, @​shaodahong and @​wlawt for their first PRs!

👓 Spec Compliance
  • babel-parser
  • babel-helper-member-expression-to-functions, babel-plugin-proposal-class-properties, babel-plugin-proposal-optional-chaining
  • babel-plugin-proposal-logical-assignment-operators
  • babel-helper-create-class-features-plugin, babel-helper-member-expression-to-functions, babel-plugin-proposal-class-properties, babel-plugin-proposal-optional-chaining
🐛 Bug Fix
💅 Polish
🏠 Internal
Committers: 11
typescript-eslint/typescript-eslint

v3.3.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-unused-expressions] handle ternary and short-circuit options (#​2194) (ee9f100)
  • typescript-estree: handle TS4.0 breaking change in TupleType (#​2197) (5d68129)
Features
  • eslint-plugin: [naming-convention] better error message and docs for prefix/suffix (#​2195) (a2ffe55)
eslint/eslint

v7.3.0

Compare Source

prettier/eslint-plugin-prettier

v3.1.4

Compare Source

  • Avoid clearing Prettier cache when not using prettierrc (#​303) (3c8e2d9)
  • build(deps-dev): bump eslint-plugin-eslint-plugin from 2.2.1 to 2.2.2 (93f7c8b)
  • build(deps-dev): bump eslint from 7.1.0 to 7.2.0 (650ac7a)
  • build(deps-dev): bump eslint-plugin-self from 1.2.0 to 1.2.1 (6449ec1)
  • build(deps-dev): bump eslint from 7.0.0 to 7.1.0 (fd30022)
  • Chore: Add CI tests for ESLint 7 (#​291) (cc2979b)
  • build(deps-dev): bump eslint-config-prettier from 6.10.1 to 6.11.0 (35a7ee6)
okonet/lint-staged

v10.2.11

Compare Source

Bug Fixes
  • run all git commands with submodule.recurse=false (#​888) (86c9ed2)
algolia/shipjs

v0.20.0

Compare Source

BREAKING CHANGE
BREAKING CHANGE

From this version, mergeStrategy no longer exists.

If you don't know what it is,

Make sure you run shipjs trigger only on the branches you've specified.

If you have a CircleCI config like the following:

version: 2
jobs:
  shipjs_trigger:
    docker:
      - image: "circleci/node:latest"
    steps:
      - checkout
      - run:
          name: Install
          command: yarn install
      - run:
          name: Triggering Ship.js to Release
          command: yarn shipjs trigger
workflows:
  version: 2
  release_if_needed:
    jobs:
      - shipjs_trigger

then, modify the last part like the following:

workflows:
  version: 2
  release_if_needed:
    jobs:
      - shipjs_trigger:
          filters:
            branches:
              only:
                - master # or whatever branch you'd like (normally your base branch)

This ensures shipjs trigger runs only on the specified branches.

If you were using mergeStrategy,

Ship.js used to have toSameBranch and toReleaseBranch strategies. Now they're gone and it only works like toSameBranch strategy. As explained above, you need to specify branches where to run shipjs trigger, though.

If you were using toReleaseBranch, there is a workaround. You can read Release Snapshot to achieve what you used to do.

Bug Fixes
webpack-contrib/terser-webpack-plugin

v3.0.6

Compare Source

v3.0.5

Compare Source

webpack/webpack-cli

v3.3.12

Compare Source

Renovate configuration

📅 Schedule: "after 10pm on sunday,before 5am on sunday" in timezone Asia/Tokyo.

🚦 Automerge: Enabled.

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

👻 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 merged commit e62cf83 into master Jun 20, 2020
@renovate renovate bot deleted the renovate/devdependencies branch June 20, 2020 20:11
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
dependencies
Projects
None yet
Milestone
No milestone
Development

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