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

fix: update terser-webpack-plugin to v1.2.4 #54

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 9, 2019

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
terser-webpack-plugin 1.2.1 -> 1.2.4 age adoption passing confidence

Release Notes

webpack-contrib/terser-webpack-plugin

v1.2.4

Compare Source

v1.2.3

Compare Source

Bug Fixes
  • invalidate cache after changing node version (675edfd)

v1.2.2

Compare Source

Bug Fixes

Configuration

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

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

♻️ Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot assigned c3dr0x and JabX Jul 9, 2019
@renovate renovate bot force-pushed the deps/webpack-focus-terser-webpack-plugin-1.2.x branch 3 times, most recently from 922d916 to 402c756 Compare July 15, 2019 12:06
@renovate renovate bot force-pushed the deps/webpack-focus-terser-webpack-plugin-1.2.x branch from 402c756 to cbf2e2b Compare July 15, 2019 12:14
@renovate renovate bot changed the title chore: update terser-webpack-plugin to v1.2.4 fix: update terser-webpack-plugin to v1.2.4 Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants