Coder Social home page Coder Social logo

salesforce-graphql's People

Contributors

greenkeeper[bot] avatar whiteabelincoln avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

salesforce-graphql's Issues

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from 23.3.2 to 23.3.3.

🚨 View failing branch.

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

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/jsforce is breaking the build 🚨

The devDependency @types/jsforce was updated from 1.9.1 to 1.9.2.

🚨 View failing branch.

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

@types/jsforce is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/express is breaking the build 🚨

The devDependency @types/express was updated from 4.16.1 to 4.17.0.

🚨 View failing branch.

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

@types/express is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from 3.1.0 to 3.2.0.

🚨 View failing branch.

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

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Commits

The new version differs by 3 commits.

  • e427d90 feat(services): add azure pipelines (#114)
  • 023d204 Use small HTTP dependency (#110)
  • 500f308 Update Readme

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of jest-junit is breaking the build 🚨

The devDependency jest-junit was updated from 5.1.0 to 5.2.0.

🚨 View failing branch.

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

jest-junit is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for v5.2.0
  • Adds rootDir support #65
  • Adds outputDirectory and outputName #62
Commits

The new version differs by 9 commits.

  • fd25452 Merge pull request #65 from IIFE/rootDir
  • 54f42a2 Use toContain matcher instead of indexOf check
  • dc46367 Allow placeholder to be used in the output option.
  • 074e95d Merge pull request #62 from Vivalldi/master
  • 352a67e Add outputDirectory and outputName;
  • 9e0b320 Merge pull request #64 from palmerj3/testEnvironmentNode
  • d24dbdc Update tests to run in node environment
  • fdbc8f1 Merge pull request #59 from cezzre/patch-1
  • ef32598 Add instructions for using "jest-junit" in CI

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of @commitlint/config-conventional is breaking the build 🚨

The devDependency @commitlint/config-conventional was updated from 7.3.0 to 7.3.1.

🚨 View failing branch.

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

@commitlint/config-conventional is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fp-ts is breaking the build 🚨

The devDependency fp-ts was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

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

fp-ts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests passed on CircleCI! (Details).
  • ci/circleci: coverage: CircleCI is running your tests (Details).
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Release Notes for 1.10.0
  • Deprecation
    • deprecate Foldable in favour of Foldable2v (*)
    • deprecate Traversable in favour of Traversable2v (*)
  • New Feature
  • Documentation
    • refactor docs layout (@gcanti)
    • add examples to Array module (@gcanti)
    • type-check the examples while generating the documentation (@gcanti)
    • comparison with ramda
    • add example and explanation for Array.member (@fozcodes)
  • Internal

(*) Foldable and Traversable will be replaced with Foldable2v and Traversable2v implementations in fp-ts@2

Commits

The new version differs by 81 commits.

  • a93149d bump version
  • 02d57d4 add TraverseComposition1, SequenceComposition1 and an example of getTraversableComposition to Traversable2v
  • 5a71e0c Docs: add examples to Foldable2v
  • 12ec897 Docs: add example for Applicative.when
  • 4a126c9 Docs: add description to ap_ methods
  • 9c0e07e Docs: add TaskEither.tryCatch example
  • d0c7eb8 fix Array.member example
  • 1ed2575 Docs: [ramda] add link to monocle-ts
  • 139bae6 Docs: [ramda] add links
  • ee85ddb Docs: comparison with ramda
  • 7e95c52 New Feature: add Array comprehension
  • 7ecaaa3 rename some Foldable2v functions (according to Array module)
  • 606ca52 rearrange Foldable2v arguments order
  • b1bb545 New Feature: add TaskEither.prototype.foldTask and rename foldM to foldTaskEither
  • 33abd99 Docs: type-check the examples while generating the documentation

There are 81 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Move src/SOQL, getFieldSet, src/util/BinaryTree, and src/util/GraphQLScalars to their own packages

These modules don't directly relate to constructing a graphql schema from a salesforce org. They are mostly utility modules and functions that I wrote to help with querying and construction.

Extracting them into their own npm packages would allow other people to use them independently of this project, and would reduce overhead and maintenance for salesforce-graphql. src/SOQL and getFieldSet especially could be useful for other developers.

An in-range update of graphql-iso-date is breaking the build 🚨

The dependency graphql-iso-date was updated from 3.5.0 to 3.6.1.

🚨 View failing branch.

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

graphql-iso-date is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for v3.6.1

Fixed issue with deployment. v3.6.0 was not published due to an issue.

Commits

The new version differs by 7 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of express is breaking the build 🚨

The devDependency express was updated from 4.16.4 to 4.17.0.

🚨 View failing branch.

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

express is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for 4.17.0
Commits

The new version differs by 53 commits.

There are 53 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/cli is breaking the build 🚨

The devDependency @commitlint/cli was updated from 7.1.2 to 7.2.0.

🚨 View failing branch.

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

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Change typescript dependency to latest once 3.0.0 is released

Because of microsoft/TypeScript#24599, builds were working in some cases, but when attempting to use the library in a typescript project building would fail because of invalid relative imports. typescript@next fixes this bug, but I don't want to track the unstable version of typescript. This issue is a reminder to change the typescript dependency to typescript@latest once typescript 3.0.0 is released (in a few weeks)

An in-range update of @types/mem is breaking the build 🚨

The devDependency @types/mem was updated from 1.1.2 to 1.1.3.

🚨 View failing branch.

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

@types/mem is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fp-ts is breaking the build 🚨

The dependency fp-ts was updated from 1.8.0 to 1.8.1.

🚨 View failing branch.

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

fp-ts is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for 1.8.1
  • Bug Fix
Commits

The new version differs by 6 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Reduce duplication between getConditionalInfo and getQueryInfo

// TODO: Reduce duplication between getConditionalInfo and getQueryInfo
if (field.kind === 'concreteCondition') {
const partitioned = partition(field.children || [], {
leafs: and(isAnnotatedFieldSet, c => isLeafField(c.configField))
, childs: and(isAnnotatedFieldSet, c => isChildField(c.configField))
, parents: and(isAnnotatedFieldSet, c => isParentField(c.configField))


This issue was generated by todo based on a TODO comment in 5f268d6 when #8 was merged. cc @WhiteAbeLincoln.

An in-range update of mem is breaking the build 🚨

The dependency mem was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

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

mem is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for v4.2.0

v4.1.0...v4.2.0

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from 1.0.0-rc.13 to 1.0.0-rc.14.

🚨 View failing branch.

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

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Commits

The new version differs by 14 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/prompt is breaking the build 🚨

The devDependency @commitlint/prompt was updated from 7.1.2 to 7.2.0.

🚨 View failing branch.

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

@commitlint/prompt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/express-graphql is breaking the build 🚨

The devDependency @types/express-graphql was updated from 0.6.1 to 0.6.2.

🚨 View failing branch.

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

@types/express-graphql is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of commitizen is breaking the build 🚨

The devDependency commitizen was updated from 3.0.4 to 3.0.5.

🚨 View failing branch.

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

commitizen is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for v3.0.5

3.0.5 (2018-11-27)

Bug Fixes

  • package: avoid depending on flatmap-stream (#591) (0eded0a)
Commits

The new version differs by 1 commits.

  • 0eded0a fix(package): avoid depending on flatmap-stream (#591)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/cli is breaking the build 🚨

The devDependency @commitlint/cli was updated from 7.2.1 to 7.3.1.

🚨 View failing branch.

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

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from 23.1.4 to 23.10.0.

🚨 View failing branch.

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

ts-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for 23.10.0

ts-jest, reloaded!

  • lots of new features including full type-checking and internal cache (see changelog)
  • improved performances
  • Babel not required anymore
  • improved (and growing) documentation
  • a ts-jest Slack community where you can find some instant help
  • end-to-end isolated testing over multiple jest, typescript and babel versions
Commits

The new version differs by 293 commits.

  • 0e5ffed chore(release): 23.10.0
  • 3665609 Merge pull request #734 from huafu/appveyor-optimizations
  • 45d44d1 Merge branch 'master' into appveyor-optimizations
  • 76e2fe5 ci(appveyor): cache npm versions as well
  • 191c464 ci(appveyor): try to improve appveyor's config
  • 0f31b42 Merge pull request #733 from huafu/fix-test-snap
  • 661853a Merge branch 'master' into fix-test-snap
  • aa7458a Merge pull request #731 from kulshekhar/dependabot/npm_and_yarn/tslint-plugin-prettier-2.0.0
  • 70775f1 ci(lint): run lint scripts in series instead of parallel
  • a18e919 style(fix): exclude package.json from tslint rules
  • 011b580 test(config): stop using snapshots for pkg versions
  • 7e5a3a1 build(deps-dev): bump tslint-plugin-prettier from 1.3.0 to 2.0.0
  • fbe90a9 Merge pull request #730 from kulshekhar/dependabot/npm_and_yarn/@types/node-10.10.1
  • a88456e build(deps-dev): bump @types/node from 10.9.4 to 10.10.1
  • 54fd239 Merge pull request #729 from kulshekhar/dependabot/npm_and_yarn/prettier-1.14.3

There are 250 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from 23.3.9 to 23.3.10.

🚨 View failing branch.

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

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/prompt is breaking the build 🚨

The devDependency @commitlint/prompt was updated from 7.2.1 to 7.3.1.

🚨 View failing branch.

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

@commitlint/prompt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/graphql-iso-date is breaking the build 🚨

The dependency @types/graphql-iso-date was updated from 3.3.0 to 3.3.1.

🚨 View failing branch.

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

@types/graphql-iso-date is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

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

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Commits

The new version differs by 7 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of isemail is breaking the build 🚨

The dependency isemail was updated from 3.1.3 to 3.1.4.

🚨 View failing branch.

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

isemail is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for v3.1.4

This patch release updates the punycode dependency for bundler compatibility, fixes the IDN-aware length check, and adds an explicit type check to the email parameter. Please note that if you were previously passing in a non-string, you would have still seen a TypeError - just from a different location.

Commits

The new version differs by 8 commits.

  • 72313d0 3.1.4
  • 05620f1 Merge pull request #191 from hapijs/fix-unicode-size-bounds
  • 20e3b8e Update punycode to latest, fix npm resolved entries
  • cb5e1c4 Fix unicode domain length limit
  • 04159e6 Merge pull request #185 from hapijs/email-type-check
  • d003d9b Branch normalize fallback behavior
  • 347826d Add explicit email type check
  • 32397f3 Update lab to 16

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of jsforce is breaking the build 🚨

The dependency jsforce was updated from 1.9.1 to 1.9.2.

🚨 View failing branch.

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

jsforce is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Commits

The new version differs by 22 commits.

  • b6bebda Merge pull request #908 from jsforce/release-1.9.2
  • 958d7cd update VERSION.js
  • 9adf6f2 change ver to 1.9.2
  • 3b604c4 Merge pull request #905 from jsforce/upgrade-vurnable-libs
  • f3e6926 add built files
  • 777abbf update libs to fix vurnerability
  • 7e5f990 Merge pull request #907 from jsforce/migrate-to-circleci
  • f3b0176 change status badge
  • 0f00f26 add browser test
  • 62b1b63 add circleci config
  • a4d3e79 fix rename test and update API version
  • 1d59817 avoid puppeteer to become browserify target
  • 3f9e567 Merge pull request #838 from nathanross/master
  • 0f42372 resolve issue #813 - bug in upsert of Collections
  • 7364893 Merge pull request #826 from HappyFerret/fix/csv-parse-error

There are 22 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Issue a pull request for GraphQLISODate that lets it parse the limited ISO8601 g...

// TODO: Issue a pull request for GraphQLISODate that lets it parse the limited ISO8601 grammar as defined
// in Appendix a of ISO3339 RFC
const configField = annotatedFields.configField
if (configField && isLeafField(configField) && configField.sftype === 'datetime') {
return right(Promise.resolve(source && new Date(source[annotatedFields.fieldName])))
}


This issue was generated by todo based on a TODO comment in 5f268d6 when #8 was merged. cc @WhiteAbeLincoln.

An in-range update of tslint-immutable is breaking the build 🚨

The devDependency tslint-immutable was updated from 4.7.0 to 4.8.0.

🚨 View failing branch.

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

tslint-immutable is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fp-ts is breaking the build 🚨

The devDependency fp-ts was updated from 1.11.2 to 1.11.3.

🚨 View failing branch.

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

fp-ts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

Release Notes for 1.11.3
  • Deprecation
    • Array
      • refine in favour of filter (@gcanti)
    • Either
      • .prototype.refineOrElse in favour of .prototype.filterOrElse (@gcanti)
      • .prototype.refineOrElseL in favour of .prototype.filterOrElseL (@gcanti)
      • fromRefinement in favour of fromPredicate (@gcanti)
    • Option
      • .prototype.refine in favour of .prototype.filter (@gcanti)
      • fromRefinement in favour of fromPredicate (@gcanti)
  • Polish
    • use built-in Record type in Record module (@gcanti)
    • add support for refinements (@gcanti)
      • Array
        • takeWhile
        • span
      • NonEmptyArray
        • .prototype.filter
      • ReaderTaskEither
        • fromPredicate
      • Record
        • filter
      • Set
        • filter
        • partition
      • StrMap
        • filter
      • TaskEither
        • .prototype.filterOrElse
        • .prototype.filterOrElseL
        • fromPredicate
      • Validation
        • fromPredicate
Commits

The new version differs by 26 commits.

  • b2c574e bump version
  • 3295662 Docs: handle method overloadings
  • a9bd313 Internal: add unsafe-docs script
  • 027b0b6 fix linting
  • 56bd67a Polish: add support for refinements to Validation.fromPredicate
  • 0aed8e9 Polish: add support for refinements to TaskEither.fromPredicate
  • 2ff33fb Polish: add support for refinements to TaskEither.prototype.filterOrElse
  • 550c0ef Polish: add support for refinements to StrMap.filter
  • fc1a7e1 Polish: add support for refinements to Set.filter
  • 3e63fbf Polish: add support for refinements to Set.filter
  • 5bcde3b Polish: use built-in Record type in Record
  • 925baf1 Polish: add support for refinements to Record.filter
  • 4aa326b Polish: add support for refinements to ReaderTaskEither.fromPredicate
  • 11356b8 Polish: add support for refinements to NonEmptyArray.prototype.filter
  • 340681a Polish: add support for refinements to Array.span

There are 26 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/jsforce is breaking the build 🚨

The dependency @types/jsforce was updated from 1.8.16 to 1.9.0.

🚨 View failing branch.

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

@types/jsforce is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: checkout: Your tests failed on CircleCI (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.