Giter Club home page Giter Club logo

flagship's People

Contributors

andyschwob avatar bodrus avatar branderbot avatar buticm avatar bweissbart avatar cauldrath avatar chukohsin avatar ckornell avatar crherman7 avatar davidrhodesbb avatar dependabot-preview[bot] avatar dependabot[bot] avatar grayontheweb avatar greenkeeper[bot] avatar huizhuz avatar jasonmosley avatar jcarvin avatar mrivasperez avatar nathan-sankbeil avatar nickburkhartbb avatar olexandor avatar olkorsia avatar pavlemilicevicbb avatar romaniukua avatar rosahbruno avatar sdenaci avatar sentiurin avatar skyeckstrom avatar varzaman avatar wsedlacek avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

flagship's Issues

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

The devDependency lerna was updated from 3.4.1 to 3.4.2.

🚨 View failing branch.

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

lerna 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
  • coverage/coveralls: Coverage pending from Coveralls.io (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.4.2

Bug Fixes

  • publish: Prevent retries during access validation so third-party registries are skipped faster (a89ae62)
  • publish: Use modern auth resolution (7ba41a6)
Commits

The new version differs by 6 commits.

  • 6afcde7 chore(release): publish v3.4.2
  • bef9a83 chore: bump transitive dependencies
  • 3d68d87 chore: bump dev dependencies
  • a89ae62 fix(publish): Prevent retries during access validation so third-party registries are skipped faster
  • 7ba41a6 fix(publish): Use modern auth resolution
  • ef47f2a docs(version): document the —yes option (#1715)

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 🌴

Fix Android Version Code

As it stands right now, any Android app with a minimum SDK version set >= 21 will be unable to be uploaded to the Google Play store due to how the versionCode is crafted:

  1. The version is first normalized:
    fs.update(
    path.android.gradlePropertiesPath(),
    /VERSION_CODE_SHORT=\d+/,
    `VERSION_CODE_SHORT=${versionLib.normalize(newVersion)}`
    );
    which converts a version to XX.YYY.ZZZ format by inserting zeros where appropriate:
    /**
    * Normalizes a version number into a standard format XX.YYY.ZZZ
    *
    * @param {string} version The version number to normalize.
    * @returns {string} A normalized version number.
    */
    export function normalize(version: string): string {
    const versionAndLabel = version.split('-');
    const parts = versionAndLabel[0].split('.');
    return [
    padZeros(parts[0], 2),
    padZeros(parts[1], 3),
    padZeros(parts[2], 3)
    ].join('');
  2. The minimum SDK version is then appended to the front of the normalized version string:
    versionCode "${rootProject.ext.minSdkVersion}${project.VERSION_CODE_SHORT}".toInteger()

Using an example version of 1.2.3 with a minSdkVersion=21, the resulting versionCode would be 2101002003, however the maximum value Google Play allows for versionCode is 2100000000. When attempting to upload any app with a versionCode > 2100000000, you are presented with the following error:

The version code of your APK or Android App Bundle is high and you risk not being able to update your APK or Android App Bundle.

There are a few possible ways to fix this issue:

  1. Adjust the normalize function to only insert zeros to a max length of 2 rather than 3 (e.g. resulting format would be XX.YY.ZZ rather than XX.YYY.ZZZ)
    • This change would affect both Android and iOS builds
  2. Adjust the Android versionCode definition to remove the minSdkVersion from the front of the versionCode

NB
This fix WILL be a breaking fix, as new version codes will be less than the currently uploaded ones. Any Android application built through Flagship and uploaded to Google Play would need to have some sort of patch in place in its individual code base to account for this change.

Change how Android project path is handled

Currently the Android project path is hardcoded to be "com.brandingbrand.reactnative.and.project_name" as specified in getNativeProjectPathAndriod [sic]:

function getNativeProjectPathAndriod(configuration: Config): string {
return resolvePathFromProject(
getMainPath(),
'java',
'com',
'brandingbrand',
'reactnative',
'and',
configuration.name.toLowerCase()
);
}

This value is used in a few places during Android init, such as constructing applicationId in build.gradle.

This is an issue for a couple of reasons:

  1. Because Flagship is now open source, application identifiers shouldn't be required to have "brandingbrand" in them
  2. We let apps define arbitrary bundle IDs in the bundleIds.android environment configuration, so it isn't obvious that the bundle ID actually needs to conform to a strict schema that consists of "com.brandingbrand.reactnative.and." followed by the name property in the environment configuration

An in-range update of react-native-masked-text is breaking the build 🚨

Version 1.9.0 of react-native-masked-text was just published.

Branch Build failing 🚨
Dependency react-native-masked-text
Current Version 1.7.2
Type dependency

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

react-native-masked-text 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 15 commits.

  • 28268a7 Merge pull request #91 from benhurott/1.9.0
  • ba79449 docs(changelog): update changelog
  • 64e1a6b docs(logo): adding cool logo =)
  • 0ee2331 feat(mask-service): adding getMask
  • 3bcd57b tests(*): adding new tests to getMask
  • 82bc4b9 refactor(core): refactoring custom mask
  • 18eea9a feat(CpfCnpj): adding auto-mask for cpf and cnpj
  • 6f02fb9 Merge branch 'ronaldozanoni-master' into 1.9.0
  • c2b1369 docs(changelog): updating changelog
  • e3602b6 Merge branch 'emiyake-patch/npm-dependencies' into 1.9.0
  • e9a8e29 merge PR 80
  • 77aebe8 merge PR 74
  • ebb576a add cpf-cnpj mask to auto detect if the document is cpf or cnpj
  • bfed6c2 moved typings dependencies to devDependencies
  • 5169774 TypeScript support for custom mask options

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 babel-plugin-react-native-web is breaking the build 🚨

Version 0.8.9 of babel-plugin-react-native-web was just published.

Branch Build failing 🚨
Dependency babel-plugin-react-native-web
Current Version 0.8.8
Type dependency

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

babel-plugin-react-native-web 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 webpack is breaking the build 🚨

Version 4.16.0 of webpack was just published.

Branch Build failing 🚨
Dependency webpack
Current Version 4.15.1
Type dependency

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

webpack 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • coverage/coveralls First build on greenkeeper/flagship/webpack-4.16.0 at 37.128% Details

Release Notes v4.16.0

Features

  • add wasm support for electron-renderer target
  • add optimization.moduleIds and optimization.chunkIds options to replace other options

Bugfixes

  • fix order of side effect evaluation for exported dependencies in side-effect-free modules
  • fix some typos
  • Support the case when passing an array to output.library.root and using a devtool
  • fix a HMR logging message issue in browser where err.stack is not set
  • add missing default extensions to the DllReferencePlugin
  • module/chunk ids in Stats now sort numerical when they are numbers
  • fix lost chunk reasons when using optimization.splitChunks.maxSize
  • fix cases where Dependency.loc is a string instead of an object

Deprecations

  • deprecated Dependency.compare in favor of compareLocations
  • optimization.namedModules is now deprecated
  • optimization.hashedModuleIds is now deprecated
  • optimization.namedChunks is now deprecated
  • optimization.occurrenceOrder is now deprecated
Commits

The new version differs by 44 commits.

  • 18d33c6 4.16.0
  • 6f72243 Merge pull request #7700 from webpack/bugfix/loc-in-single-entry-and-loader-plugin
  • 3366421 Merge pull request #7663 from webpack/feature/automatic-name-prefix
  • 8891bd5 Merge pull request #7696 from webpack/bugfix/max-size-reasons
  • 365beb1 Merge pull request #7699 from webpack/ci/upgrade-jest
  • b93225a add types and fix incorrect loc type
  • f0cd451 do not instrument node_modules
  • baa450d Merge pull request #7698 from webpack/bugfix/deprecated
  • b32a4f5 Merge branch 'master' into bugfix/max-size-reasons
  • f95d0f0 Merge pull request #7695 from webpack/bugfix/sort-ids-stats
  • 1869d8e Merge pull request #7694 from webpack/bugfix/loc-in-context
  • 78d8f4a Merge pull request #7691 from mathiasbynens/mjs
  • 8876514 replace deprecated method
  • a482565 upgrade jest
  • 692faf2 sort ids in Stats numerical

There are 44 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 react-native-sensitive-info is breaking the build 🚨

Version 5.2.3 of react-native-sensitive-info was just published.

Branch Build failing 🚨
Dependency react-native-sensitive-info
Current Version 5.2.2
Type dependency

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

react-native-sensitive-info 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
  • coverage/coveralls: Coverage pending from Coveralls.io (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v5.2.3

This was released as a beta version, so to install just run:

or

yarn add react-native-sensitive-info@beta
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 🌴

Complete Shopify API

I have the code in another project and I plan to port it over to the fsshopify package.

An in-range update of react-native-svg is breaking the build 🚨

Version 6.5.1 of react-native-svg was just published.

Branch Build failing 🚨
Dependency react-native-svg
Current Version 6.5.0
Type dependency

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

react-native-svg 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

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 @types/react-dom is breaking the build 🚨

The devDependency @types/react-dom was updated from 16.0.7 to 16.0.8.

🚨 View failing branch.

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

@types/react-dom 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/@types/react-dom-16.0.8 at 36.386% (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 npm-run-all is breaking the build 🚨

The devDependency npm-run-all was updated from 4.1.3 to 4.1.4.

🚨 View failing branch.

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

npm-run-all 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/npm-run-all-4.1.4 at 36.533% (Details).

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 @commitlint/travis-cli is breaking the build 🚨

The devDependency @commitlint/travis-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/travis-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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/@commitlint/travis-cli-7.2.0 at 36.386% (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/react-native-push-notification is breaking the build 🚨

The devDependency @types/react-native-push-notification was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

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

@types/react-native-push-notification 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/@types/react-native-push-notification-3.0.3 at 36.386% (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 rimraf is breaking the build 🚨

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

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

rimraf 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/rimraf-2.6.3 at 36.533% (Details).

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 🌴

Half Screen Modal Position Prop

Add a prop to set the position of the 1/2 screen modal component (top, bottom[default], center).

This will allow the component to have more use cases.

A 'capsule' component for UI

Basically a non-working button with text for step markers ('1', '2', '3', etc.), any other UI elements that look like buttons but aren't clickable.

Add ability to specify brand

When developing an app with Flagship for multiple brands that utilize the same overall structure but differ in some way for each specific brand, it would be handy to be able to initialize the app with brand parameters.

Possible implementation:
Add functions in the init.ts command in the flagship module that would look for brand.brandName.js files in the project env (or new brand) folder that would combine this information with the environment information for the final env.js file.

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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/@commitlint/cli-7.2.0 at 36.386% (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 react-native-web is breaking the build 🚨

The devDependency react-native-web was updated from 0.8.10 to 0.8.11.

🚨 View failing branch.

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

react-native-web 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
  • coverage/coveralls: Coverage pending from Coveralls.io (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (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 react-native-navigation is breaking the build 🚨

Version 1.1.477 of react-native-navigation was just published.

Branch Build failing 🚨
Dependency react-native-navigation
Current Version 1.1.476
Type dependency

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

react-native-navigation 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits ahead by 2, behind by 1.

  • 93cdd6f v1.1.477 [ci skip]
  • 734e241 revert screen change event condition and global scree event condition before 1.1.464 (#3548)

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 webpack-cli is breaking the build 🚨

Version 3.1.0 of webpack-cli was just published.

Branch Build failing 🚨
Dependency webpack-cli
Current Version 3.0.8
Type dependency

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

webpack-cli 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • coverage/coveralls First build on greenkeeper/flagship/webpack-cli-3.1.0 at 36.954% Details

Commits

The new version differs by 57 commits.

  • a157ce1 chore: v.3.1.0
  • ca0c41f tests(fix): bin test outputs (#552)
  • 87dd419 chore: fix minor build infra
  • a2f10e9 chore: add missing READMES to packages (#545)
  • d6a433b chore(pkg): Update eslint-plugin-node to the latest version 🚀
  • 16d0790 feat(cli): Typescript support
  • a3d41fb chore(package): update lockfile
  • 817f99c chore: update pkg.lock
  • fdc82b9 chore: update gitignore
  • 507a4a6 chore(package): update eslint-plugin-node to version 7.0.0
  • 8adbe9e fix(generators): named export
  • 938e5f9 tests(migrate): fix transforms order issue
  • ce956c0 fix: default named import bug
  • 971b31a chore(generate-loader,plugin): add typescript support
  • 47702cb feat(utils): add typescript support

There are 57 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 request is breaking the build 🚨

Version 2.88.0 of request was just published.

Branch Build failing 🚨
Dependency request
Current Version 2.87.0
Type dependency

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

request 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
  • coverage/coveralls: First build on greenkeeper/flagship/request-2.88.0 at 36.456% (Details).

Commits

The new version differs by 13 commits.

  • 6420240 2.88.0
  • bd22e21 fix: massive dependency upgrade, fixes all production vulnerabilities
  • 925849a Merge pull request #2996 from kwonoj/fix-uuid
  • 7b68551 fix(uuid): import versioned uuid
  • 5797963 Merge pull request #2994 from dlecocq/oauth-sign-0.9.0
  • 628ff5e Update to oauth-sign 0.9.0
  • 10987ef Merge pull request #2993 from simov/fix-header-tests
  • cd848af These are not going to fail if there is a server listening on those ports
  • a92e138 #515, #2894 Strip port suffix from Host header if the protocol is known. (#2904)
  • 45ffc4b Improve AWS SigV4 support. (#2791)
  • a121270 Merge pull request #2977 from simov/update-cert
  • bd16414 Update test certificates
  • 536f0e7 2.87.1

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.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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/@types/jest-23.3.3 at 36.386% (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 🌴

Broken Android Build, Differing Versions Of Google Play Services

Steps:

FAILURE: Build failed with an exception.
* What went wrong:
Failed to capture snapshot of input files for task ':react-native-maps:compileReleaseAidl' property 'importDirs' during up-to-date check.
> The library com.google.android.gms:play-services-basement is being requested by various other libraries at [[15.0.1,15.0.1]], but resolves to 10.2.4. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

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

Version 4.17.1 of @types/lodash-es was just published.

Branch Build failing 🚨
Dependency @types/lodash-es
Current Version 4.17.0
Type devDependency

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

@types/lodash-es 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
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 react-id-swiper is breaking the build 🚨

Version 1.6.7 of react-id-swiper was just published.

Branch Build failing 🚨
Dependency react-id-swiper
Current Version 1.6.6
Type dependency

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

react-id-swiper 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits ahead by 5, behind by 2.

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/url-parse is breaking the build 🚨

Version 1.4.0 of @types/url-parse was just published.

Branch Build failing 🚨
Dependency @types/url-parse
Current Version 1.1.1
Type devDependency

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

@types/url-parse 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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/react is breaking the build 🚨

Version 16.4.7 of @types/react was just published.

Branch Build failing 🚨
Dependency @types/react
Current Version 16.4.6
Type devDependency

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

@types/react 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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/memoize-one is breaking the build 🚨

The devDependency @types/memoize-one was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

@types/memoize-one 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (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/yargs is breaking the build 🚨

Version 11.1.0 of @types/yargs was just published.

Branch Build failing 🚨
Dependency @types/yargs
Current Version 11.0.0
Type devDependency

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

@types/yargs 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
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 react-native-i18n is breaking the build 🚨

Version 2.0.13 of react-native-i18n was just published.

Branch Build failing 🚨
Dependency react-native-i18n
Current Version 2.0.12
Type dependency

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

react-native-i18n 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
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v2.0.13
  • Use Android SDK version variables from root project
  • Add React dependency in podspec file
Commits

The new version differs by 9 commits.

  • 4f07374 Bump version
  • c5a0ac4 Merge pull request #185 from rayronvictor/master
  • 32deead Merge pull request #195 from olegserov/patch-1
  • f66297e Fix RNI18n.podspec to avoid "Error installing RNI18n"
  • f6982cf Using SDK Version variables from root project
  • 39d027c Merge pull request #181 from c100k/patch-1
  • 0f7572c Add missing flow annotations
  • 356a427 Merge pull request #180 from shic/master
  • c4ad98a Update readme to make it more clear for most users

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/react-router-dom is breaking the build 🚨

Version 4.3.0 of @types/react-router-dom was just published.

Branch Build failing 🚨
Dependency @types/react-router-dom
Current Version 4.2.7
Type devDependency

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

@types/react-router-dom 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
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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/react-redux is breaking the build 🚨

Version 6.0.5 of @types/react-redux was just published.

Branch Build failing 🚨
Dependency @types/react-redux
Current Version 6.0.4
Type devDependency

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

@types/react-redux 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
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 🌴

React-native-camera package fails to build

Steps to reproduce:

  • Download `react-native-camera'
  • Init project
  • Run project using yarn android

FAILURE: Build failed with an exception.

  • What went wrong:
    Failed to capture snapshot of input files for task ':react-native-camera:compileReleaseAidl' property 'importDirs' during up-to-date check.

The library com.google.android.gms:play-services-basement is being requested by various other libraries at [[15.0.1,15.0.1]], but resolves to 12.0.1. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

An in-range update of url-parse is breaking the build 🚨

Version 1.4.3 of url-parse was just published.

Branch Build failing 🚨
Dependency url-parse
Current Version 1.4.1
Type dependency

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

url-parse 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 7 commits.

  • 426e929 [dist] 1.4.3
  • d7b582e [security] Added missing SECURITY.md
  • 53b1794 [security] Sanitize paths, hosts before parsing.
  • f60fa4e chore(package): update sauce-browsers to version 2.0.0 (#149)
  • 3cc810c [test] Remove Opera from the list of browsers to test
  • da8cddb [dist] 1.4.2
  • 56c0573 URL -> Url (#148)

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 react-native-push-notification is breaking the build 🚨

Version 3.1.1 of react-native-push-notification was just published.

Branch Build failing 🚨
Dependency react-native-push-notification
Current Version 3.0.2
Type dependency

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

react-native-push-notification 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 55 commits.

  • e6de911 PR links in changelog
  • 0d19d1f Added lokg of token (to copy/past easily from Android log)
  • 6be5ed4 Corrected changelog links
  • dd8b140 Added Changelor in Readme
  • 7562679 Merge branch 'example-app'
  • 1c6d7b0 Update to v3.1.1
  • d5afc87 Example app is added in Readme
  • 5b53901 Remote notifications now work
  • 41d42a0 Merge branch 'master' into example-app
  • 44cb230 Merge pull request #717 from avencat/feature/firebase
  • 5318359 Merge pull request #744 from chatterbugapp/pp-support-twilio-message
  • 8308e13 Begin of work on Remote push notifications testing
  • 00ddc39 Different notifications for scheduled and instantaneous notif
  • 1455d0c Changed Display Name of app
  • bb2e464 Corrected babelrc for react-native

There are 55 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 true-case-path is breaking the build 🚨

Version 1.0.3 of true-case-path was just published.

Branch Build failing 🚨
Dependency true-case-path
Current Version 1.0.2
Type devDependency

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

true-case-path 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

  • a162300 1.0.3
  • d20c539 Merge pull request #7 from realityking/glob
  • abcf01f Merge pull request #6 from devoto13/patch-1
  • 373c14b Update glob to version 7.1.2
  • 1a7b123 Use valid SPDX license identifier in package.json

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.

Update dependencies to fix vulnerability

yarn audit suggests that we should update those dependencies to fix vulnerability

high:
ws >= 3.3.1

medium:
morgan >=1.9.1

low:
merge >=1.2.1
lodash >= 4.17.5

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

There have been updates to the react monorepoundefined

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/flagship/monorepo.react-16.5.1 at 36.386% (Details).

Release Notes for v16.5.1

16.5.1 (September 13, 2018)

React

  • Improve the warning when React.forwardRef receives an unexpected number of arguments. (@andresroberto in #13636)

React DOM

  • Fix a regression in unstable exports used by React Native Web. (@aweary in #13598)
  • Fix a crash when component defines a method called isReactComponent. (@gaearon in #13608)
  • Fix a crash in development mode in IE9 when printing a warning. (@link-alex in #13620)
  • Provide a better error message when running react-dom/profiling with schedule/tracking. (@bvaughn in #13605)
  • If a ForwardRef component defines a displayName, use it in warnings. (@probablyup in #13615)

Schedule (Experimental)

  • Add a separate profiling entry point at schedule/tracking-profiling. (@bvaughn in #13605)
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/config-lerna-scopes is breaking the build 🚨

The devDependency @commitlint/config-lerna-scopes was updated from 7.1.2 to 7.2.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-lerna-scopes 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (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.