Skip to content

An in-range update of copy-webpack-plugin is breaking the build 🚨 #165

@greenkeeper

Description

@greenkeeper

Version 4.1.0 of copy-webpack-plugin just got published.

Branch Build failing 🚨
Dependency copy-webpack-plugin
Current Version 4.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As copy-webpack-plugin is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • semaphoreci The build failed on Semaphore. Details

Commits

The new version differs by 36 commits ahead by 36, behind by 33.

  • 3a95eab chore(release): 4.1.0
  • 73aab35 chore: Adds contrib release tooling
  • de46fde fix: Memory leak in watch mode and use Set for performance (#130)
  • 79f30ab docs: Fix travis url
  • dda7ac5 docs: Update to config readme format
  • edabbf6 chore: Update package meta
  • 75c6f08 chore: Adds changelog
  • ec44b72 chore: Change license to JS Foundation (#138)
  • 7844603 chore(release): 4.0.1 (#96)
  • 54545db ci: Added Appveyor for Windows testing (#94)
  • 405d1ec feat: Added non-wildcard glob support
  • 1b2c21a fix: Fixed glob as object
  • ad62899 fix: Improved Windows compatibility (#85)
  • 1a441d1 chore(release): 4.0.0 (#83)
  • f5d487d refactor: Changed default concurrency to 100 for EMFILE/ENFILE issues (#82)

There are 36 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions