Skip to content

An in-range update of keyv-postgres is breaking the build 🚨 #4

@greenkeeper

Description

@greenkeeper

Version 1.0.0 of keyv-postgres just got published.

Branch Build failing 🚨
Dependency keyv-postgres
Current Version 0.1.0
Type devDependency

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

As keyv-postgres 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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 13 commits.

  • 4b2a1cc 1.0.0
  • eccd695 Only accept opts object as constructor argument
  • 1173054 Lock dependency versions
  • b046148 Test against Postgres 9.5 on Travis
  • 1cea622 Update to keyv-sql 0.2.3 for latest Postgres compat
  • 05561f2 Remove sequelize dependencies
  • 14380fa Don't use obj destructuring for Node.js 4 compat
  • da2a55e Format pq query results as array of rows for keyv-sql
  • 66e86cc Use keyv-sql instead of keyv-sequelize
  • 83a6417 Remove Greenkeeper badge
  • 1f13150 Merge pull request #1 from lukechilds/greenkeeper/initial
  • 33c8f89 Keyvpostgres => KeyvPostgres
  • e63b553 docs(readme): add Greenkeeper badge

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

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions