Git Product home page Git Product logo

blog-api's Introduction

Welcome to my GitHub pastorsj's Github Stats

  • Learning the ins and outs of data science
  • Data Scientist at Deloitte working in Generative AI/Anomaly Detection space
  • Commerical Full Stack Application Developer

blog-api's People

Contributors

greenkeeper[bot] avatar pastorsj avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

Forkers

blmsl andreif13

blog-api's Issues

An in-range update of webpack-cli is breaking the build ๐Ÿšจ

The devDependency webpack-cli was updated from 3.1.2 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.

webpack-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 could not complete due to an error (Details).

Commits

The new version differs by 124 commits.

  • 6253a73 chore: v.3.2.0
  • 0c3be76 chore: make tests pass
  • 0b6bab3 chore: better defaults
  • 78436ff chore: add-on -> scaffold
  • 3281372 chore: simplify clean-all script
  • b0f4a0f chore: addon -> scaffold
  • 82c9ea8 chore: update lockfiles
  • a3fe013 Merge pull request #716 from EvsChen/dist-scaffold
  • f9bb82d Merge pull request #693 from lakatostamas/feature/find-config-recursively
  • 3ec2e9d chore: resolve conflict
  • 83602d4 chore: update package lock and scripts
  • d82b016 Merge pull request #720 from rishabh3112/patch-7
  • 4d9c847 Merge pull request #723 from eavichay/patch-1
  • 4b2a127 docs: improve the docs (#722)
  • 9ad8c1d See #721

There are 124 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 eslint is breaking the build ๐Ÿšจ

The devDependency eslint was updated from 5.13.0 to 5.14.0.

๐Ÿšจ View failing branch.

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

eslint 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).

Release Notes for v5.14.0
  • 85a04b3 Fix: adds conditional for separateRequires in one-var (fixes #10179) (#10980) (Scott Stern)
  • 0c02932 Upgrade: [email protected] (#11401) (Ilya Volodin)
  • 104ae88 Docs: Update governance doc with reviewers status (#11399) (Nicholas C. Zakas)
  • ab8ac6a Fix: Support boundary spread elements in sort-keys (#11158) (Jakub Roลผek)
  • a23d197 New: add allowSingleLineBlocks opt. to padded-blocks rule (fixes #7145) (#11243) (richie3366)
  • e25e7aa Fix: comma-spacing ignore comma before closing paren (fixes #11295) (#11374) (Pig Fang)
  • a1f7c44 Docs: fix space-before-blocks correct code for "classes": "never" (#11391) (PoziWorld)
  • 14f58a2 Docs: fix grammar in object-curly-spacing docs (#11389) (PoziWorld)
  • d3e9a27 Docs: fix grammar in โ€œthose who saysโ€ (#11390) (PoziWorld)
  • ea8e804 Docs: Add note about support for object spread (fixes #11136) (#11395) (Steven Thomas)
  • 95aa3fd Docs: Update README team and sponsors (ESLint Jenkins)
  • 51c4972 Update: Behavior of --init (fixes #11105) (#11332) (Nicholas C. Zakas)
  • ad7a380 Docs: Update README team and sponsors (ESLint Jenkins)
  • 550de1e Update: use default keyword in JSON schema (fixes #9929) (#11288) (Pig Fang)
  • 983c520 Update: Use 'readonly' and 'writable' for globals (fixes #11359) (#11384) (Nicholas C. Zakas)
  • f1d3a7e Upgrade: some deps (fixes #11372) (#11373) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 3e0c417 Docs: Fix grammar in โ€œthereโ€™s nothing prevent youโ€ (#11385) (PoziWorld)
  • de988bc Docs: Fix grammar: Spacing improve -> Spacing improves (#11386) (PoziWorld)
  • 1309dfd Revert "Build: fix test failure on Node 11 (#11100)" (#11375) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 1e56897 Docs: โ€œthe function actually useโ€: use -> uses (#11380) (PoziWorld)
  • 5a71bc9 Docs: Update README team and sponsors (ESLint Jenkins)
  • 82a58ce Docs: Update README team and sponsors (ESLint Jenkins)
  • 546d355 Docs: Update README with latest sponsors/team data (#11378) (Nicholas C. Zakas)
  • c0df9fe Docs: ... is not an operator (#11232) (Felix Kling)
  • 7ecfdef Docs: update typescript parser (refs #11368) (#11369) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 3c90dd7 Update: remove prefer-spread autofix (fixes #11330) (#11365) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 5eb3121 Update: add fixer for prefer-destructuring (fixes #11151) (#11301) (golopot)
  • 173eb38 Docs: Clarify ecmaVersion doesn't imply globals (refs #9812) (#11364) (Keith Maxwell)
  • 84ce72f Fix: Remove extraneous linefeeds in one-var fixer (fixes #10741) (#10955) (st-sloth)
  • 389362a Docs: clarify motivation for no-prototype-builtins (#11356) (Teddy Katz)
  • 533d240 Update: no-shadow-restricted-names lets unassigned vars shadow undefined (#11341) (Teddy Katz)
  • d0e823a Update: Make --init run js config files through linter (fixes #9947) (#11337) (Brian Kurek)
  • 92fc2f4 Fix: CircularJSON dependency warning (fixes #11052) (#11314) (Terry)
  • 4dd19a3 Docs: mention 'prefer-spread' in docs of 'no-useless-call' (#11348) (Klaus Meinhardt)
  • 4fd83d5 Docs: fix a misleading example in one-var (#11350) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 9441ce7 Chore: update incorrect tests to fix build failing (#11354) (่–›ๅฎš่ฐ”็š„็Œซ)
Commits

The new version differs by 38 commits.

  • af9688b 5.14.0
  • 0ce3ac7 Build: changelog update for 5.14.0
  • 85a04b3 Fix: adds conditional for separateRequires in one-var (fixes #10179) (#10980)
  • 0c02932 Upgrade: [email protected] (#11401)
  • 104ae88 Docs: Update governance doc with reviewers status (#11399)
  • ab8ac6a Fix: Support boundary spread elements in sort-keys (#11158)
  • a23d197 New: add allowSingleLineBlocks opt. to padded-blocks rule (fixes #7145) (#11243)
  • e25e7aa Fix: comma-spacing ignore comma before closing paren (fixes #11295) (#11374)
  • a1f7c44 Docs: fix space-before-blocks correct code for "classes": "never" (#11391)
  • 14f58a2 Docs: fix grammar in object-curly-spacing docs (#11389)
  • d3e9a27 Docs: fix grammar in โ€œthose who saysโ€ (#11390)
  • ea8e804 Docs: Add note about support for object spread (fixes #11136) (#11395)
  • 95aa3fd Docs: Update README team and sponsors
  • 51c4972 Update: Behavior of --init (fixes #11105) (#11332)
  • ad7a380 Docs: Update README team and sponsors

There are 38 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 ๐ŸŒด

Secure DB setup

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[x] Support request

Current behavior

Both databases are relatively insecure.

Expected behavior

Each database should be protected according to normal standards

What is the motivation for this change?

Security

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of coveralls is breaking the build ๐Ÿšจ

The devDependency coveralls 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.

coveralls 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).

Release Notes for Dependency security updates

As suggested by NPM and Snyk.

Commits

The new version differs by 1 commits.

  • aa2519c dependency security audit fixes from npm & snyk (#210)

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 mongoose is breaking the build ๐Ÿšจ

The dependency mongoose was updated from 5.3.14 to 5.3.15.

๐Ÿšจ View failing branch.

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

mongoose 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 31 commits.

  • d6ff8d2 chore: release 5.3.15
  • 8332e87 docs(jest): add further reading section
  • 48912de fix(query): throw helpful error if non-object passed to Query#setOptions()
  • 9ac9d48 Merge pull request #7297 from Automattic/gh7280
  • 27189c2 fix: handle orFail() with findOneAndUpdate()
  • 355e49f fix(query): run map() before post hooks
  • 9023a6e Revert "fix(query): handle findOneAndUpdate() and findOneAndDelete() with orFail()"
  • b8cfb34 style: fix lint
  • 956dd58 fix(document): continue running validateSync() for all elements in doc array after first error
  • a099d95 test(document): repro #6746
  • 628a278 chore: clean up api docs issue
  • d7be77f fix(query): handle findOneAndUpdate() and findOneAndDelete() with orFail()
  • fb94563 test(query): repro #7280
  • 553868c fix(populate): support populating individual subdoc path in document array
  • b36003f test(populate): repro #7273

There are 31 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 ๐ŸŒด

Automatic/Manual DB backups

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[x] Support request

Current behavior

Currently, if I start the docker container for the database and then completely kill it, the db is deleted. We need an automated solution.

Expected behavior

I should be able to specify a location or manual run a command to backup the db.

What is the motivation for this change?

Persistent db state...

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of nodemon is breaking the build ๐Ÿšจ

The dependency nodemon was updated from 1.18.5 to 1.18.6.

๐Ÿšจ View failing branch.

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

nodemon 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 for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

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 ๐ŸŒด

Users are able to access articles written by other users that are not themselves

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Support request

Current behavior

If I am a regular user and I acquire a jwt, I can essentially write articles for other people...

Expected behavior

This probably should not be happening...

What is the motivation for this change?

Security issues...

Environment



- Node version: 8.5.0
- Platform:  Mac, Linux, Windows

Others:

This needs to be fixed immediately before going to production

System Testing

Acceptance Criteria

  • Fake backend for blog testing
  • Unit tests for critical parts
  • Add code coverage
  • Ensure that this is testable on travis
  • Add code coverage

Push Notification Support

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Support request

Current behavior

To support async push notifications, the api must be updated to allow for this.

Expected behavior

What is the motivation for this change?

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of eslint-loader is breaking the build ๐Ÿšจ

The devDependency eslint-loader was updated from 2.1.1 to 2.1.2.

๐Ÿšจ View failing branch.

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

eslint-loader 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).

Release Notes for 2.1.2
Commits

The new version differs by 2 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 supertest is breaking the build ๐Ÿšจ

The devDependency supertest was updated from 3.3.0 to 3.4.0.

๐Ÿšจ View failing branch.

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

supertest 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).

Release Notes for v3.4.0
  • PR-532 - Packages updated, pipeline more explicit, documentation updated (thanks @rimiti)
  • PR-517 - Documentation updated (thanks @oprogramador)
  • PR-513 - Use more robust Array instance check (thanks @rubendg)
Commits

The new version differs by 14 commits.

  • 5640ac9 3.4.0
  • 60f8a9e Merge pull request #532 from visionmedia/v3.4.0
  • 43bfae1 doc(History.md) changelog updated
  • fc1568d doc(README.md) cookie example added
  • 3192d96 chore(package-lock.json) file updated
  • b3d271f chore(package.json) blocks reorganized, nock removed
  • aeae0f3 chore(.travis.yml) pipeline more explicit
  • 53feddc chore(test/supertest.js) obscure test removed
  • 50c59d6 Merge pull request #519 from oprogramador/patch-3
  • 6ca3897 Merge pull request #517 from oprogramador/patch-2
  • 0146d81 auth info in README
  • d853b37 fix typo in README
  • 8158979 Merge pull request #513 from rubendg/use-isarray
  • 550613b Use more robust Array instance check

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 ๐ŸŒด

I got a question about errors

Hello! Its just a question. I dunno where to asking you so try to ask you here. I started testing my apps and have alot of questions thats why I here. I got the question. Cant understand mechanic of your errors handlers.

// development error handler
// will print stacktrace
if (app.get('env') === 'development') {
    app.use((err, req, res) => {
        if (err.name === 'UnauthorizedError') {
            res.status(401).send({ error: err });
        } else {
            res.status(err.status || 500);
        }
        log.critical(err);
    });
}

// production error handler
// no stacktraces leaked to user
app.use((err, req, res) => {
    if (err.name === 'UnauthorizedError') {
        res.status(401).send({ error: err });
    } else {
        res.status(err.status || 500);
    }
    log.critical(err);
});

There is two same structured routes. But you said that first will show errors stack, and the second - not. Why? Thanks!

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! ๐ŸŽŠ

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If youโ€™re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didnโ€™t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didnโ€™t touch job or matrix configurations because these tend to be quite specific and complex, and itโ€™s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what youโ€™re doing it may require additional work or may not be applicable at all. Weโ€™re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, Iโ€™m a humble robot and wonโ€™t feel rejected ๐Ÿค–


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 ๐ŸŒด

Update README

Include high-level description of the API, a link to the api documentation, and a link to TravisCI/CircleCI

Fix error messages output

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Support request

Current behavior

Error messages can be sent back without any message at all

Expected behavior

All error messages should be human readable to a point

What is the motivation for this change?

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of aws-sdk is breaking the build ๐Ÿšจ

The dependency aws-sdk was updated from 2.563.0 to 2.564.0.

๐Ÿšจ View failing branch.

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

aws-sdk 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 for Release v2.564.0

See changelog for more information.

Commits

The new version differs by 3 commits.

  • 75d284f Updates SDK to v2.564.0
  • 1ca7b98 Allow shortcutting in customBackoff based on error (#2898)
  • ff22c95 chore: use ^ to allow relaxed versions (#2933)

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-loader is breaking the build ๐Ÿšจ

The dependency babel-loader was updated from 8.0.4 to 8.0.5.

๐Ÿšจ View failing branch.

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

babel-loader 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 for 8.0.5
  • Update find-cache-dir to 2.0
Commits

The new version differs by 8 commits.

  • 20c9e0e 8.0.5
  • de51b5d chore: Update ava
  • 66f92af Remove docs mention about sourceMap option being ignored (#750)
  • 6df8af1 Update dependencies and run all tests (#745)
  • 2c61de5 Add node 11 and 10 (#744)
  • 1bda840 Fix config issue in example (#708)
  • 364387d Merge pull request #698 from MattGurneyAMP/patch-1
  • 98f936d Fix license header and link

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 ๐ŸŒด

Added an endpoint for graphql

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Support request

Current behavior

I am unable to use graphql queries to get information from the api

Expected behavior

The opposite of the above

What is the motivation for this change?

Environment



- Node version: XX  
- Platform:  

Others:

Refreshing page in production leads to page not found

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Support request

Current behavior

When I refresh the page in production, the page returns a Not Found error. This seems to be nginx related.

Expected behavior

When I refresh the page, I expect the page to remain on the same page as before, unless I am not authenticated.

What is the motivation for this change?

User friendliness and somewhat security related.

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of aws-sdk is breaking the build ๐Ÿšจ

The dependency aws-sdk was updated from 2.350.0 to 2.351.0.

๐Ÿšจ View failing branch.

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

aws-sdk 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 for Release v2.351.0

See changelog for more information.

Commits

The new version differs by 3 commits.

  • 70cbaa7 Updates SDK to v2.351.0
  • 4073d3d Merge pull request #2342 from srchase/npmignore-additions
  • 13b0dd3 updated npmignore, fix for issue #2341

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 mongoose is breaking the build ๐Ÿšจ

The dependency mongoose was updated from 5.5.10 to 5.5.11.

๐Ÿšจ View failing branch.

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

mongoose 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.

  • 09bc1a9 chore: release 5.5.11
  • 4d09963 refactor(discriminator): use one consolidated getConstructor() function to get the correct discriminator
  • ec01f4f fix(discriminator): allow numeric discriminator keys for embedded discriminators
  • e91fca1 test(discriminator): repro #7808
  • dc56c43 Merge pull request #7784 from Automattic/chore-node-12
  • c4fd03a chore: now working on 5.5.11
  • 10e8961 chore: add node 12 to travis

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 ๐ŸŒด

Create templates

Acceptance Criteria

  • Issue template
  • PR template
  • Code of Conduct template

An in-range update of cookie-parser is breaking the build ๐Ÿšจ

The dependency cookie-parser was updated from 1.4.3 to 1.4.4.

๐Ÿšจ View failing branch.

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

cookie-parser 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 63 commits.

There are 63 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 jsonwebtoken is breaking the build ๐Ÿšจ

The dependency jsonwebtoken was updated from 8.4.0 to 8.5.0.

๐Ÿšจ View failing branch.

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

jsonwebtoken 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 8 commits.

  • 1c0de55 8.5.0
  • eefb9d9 feat: add PS JWA support for applicable node versions (#573)
  • 8737789 Add complete option in jwt.verify (#522)
  • 7b60c12 Force use_strict during testing (#577)
  • 0c24fe6 Fix 'cert' token which isn't a cert (#554)
  • da8f55c ci: remove nsp from tests (#569)
  • 5147852 Add tests for private claims in the payload (#555)
  • 7eebbc7 Refactor tests related to jti and jwtid (#544)

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 ๐ŸŒด

All articles are returned no matter whether the authors wants them to

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Support request

Current behavior

All articles are returned when in fact only the articles that are published should be returned.

Expected behavior

Only articles that are published should be returned. This includes updating the tags route.

What is the motivation for this change?

Authors don't want to create articles that are immediately published if they are just writing a draft.

Environment



- Node version: 8.5.0
- Platform:  Mac, Linux

Others:

An in-range update of graphql is breaking the build ๐Ÿšจ

The dependency graphql was updated from 14.0.2 to 14.1.0.

๐Ÿšจ View failing branch.

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

graphql 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 for v14.1.0

New:

  • Added assertSchema and assertDirective (#1580)
  • Adds additional type extension validation (#1643)

Fixes:

  • Improves flow type definitions
  • Adds back in support for node 9, and tests for node 11. node >= 6 is currently supported.
  • Allows custom node inspect (#1605)
  • Correctly handles newlines in block strings (#1637)
Commits

The new version differs by 109 commits.

  • da61380 14.1.0
  • 4de99f7 Merge branch 'OneCyrus-feat_listTypeForError'
  • 0a731a5 Prettier and fix tests
  • a6676dc Merge branch 'feat_listTypeForError' of https://github.com/OneCyrus/graphql-js into OneCyrus-feat_listTypeForError
  • 37c022d buildClientSchema: add missing tests for introspection validations (#1666)
  • 3fef0d4 Enable Flow on buildClientSchema tests (#1665)
  • 6876587 Move $DisableFlowOnNegativeTest to more precise locations (#1664)
  • b747bb4 changed type error message
  • 8d7a5fd Merge schema validation tests with other schema tests (#1663)
  • 6741ac2 Add tests for GraphQLDirective (#1662)
  • d48e481 Move isInputType & isOutputType test to rest of predicates test (#1661)
  • 4cdc8e2 Update Flow to 0.90.0 (#1660)
  • 9f85d51 Remove excessive invariants (#1658)
  • 0818c18 ignore .nyc_output dir (#1657)
  • 9e40465 Move polyfills into separate dir and exclude them from coverage (#1656)

There are 109 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 ๐ŸŒด

Dockerize application

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Support request

Current behavior

This application is being deployed in a way where the server has to be setup beforehand. I should be able to move between servers easily, so using docker is the obvious solution.

Expected behavior

See above.

What is the motivation for this change?

Again, see above

Environment



- Node version: XX  
- Platform:  

Others:

An in-range update of yargs is breaking the build ๐Ÿšจ

The dependency yargs was updated from 13.2.2 to 13.2.4.

๐Ÿšจ View failing branch.

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

yargs 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 14 commits.

  • a6e67f1 chore(release): 13.2.4
  • fc13476 chore: update standard-verison dependency
  • bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
  • a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
  • b4f8018 build: add .versionrc that hides test/build
  • 0c39183 chore(release): 13.2.3
  • 08e0746 chore: update deps (#1340)
  • 843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
  • 84cac07 docs: restore removed changelog of v13.2.0 (#1337)
  • b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
  • c294d1b test: accept differently formatted output (#1327)
  • ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
  • 0295132 fix: address issues with dutch translation (#1316)
  • 9f2468e doc: clarify parserConfiguration object structure (#1309)

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 babel7 is breaking the build ๐Ÿšจ

There have been updates to the babel7 monorepo:

    • The dependency @babel/cli was updated from 7.1.5 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.

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

babel7 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 helmet is breaking the build ๐Ÿšจ

The dependency helmet was updated from 3.15.0 to 3.15.1.

๐Ÿšจ View failing branch.

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

helmet 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 4 commits.

  • f545a94 3.15.1
  • ca50146 Deprecate hpkp
  • 6458cd5 Update license year for 2019
  • 2dba625 Update devDependencies to latest versions and fix warnings

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 ๐ŸŒด

Progressive image loading/saving

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Support request

Current behavior

To accomplish progressive image loading on the UI, there will need to be some changes on the API side.

Expected behavior

What is the motivation for this change?

Environment



- Node version: XX  
- Platform:  

Others:

Allow for tags

Implementation Thoughts

  • Controller for tags
  • Routes for getting tags, posting tags, deleting tags
  • Autocomplete feature for getting tags
  • Redis for storing tags

An in-range update of webpack is breaking the build ๐Ÿšจ

The devDependency webpack was updated from 4.26.1 to 4.27.0.

๐Ÿšจ View failing branch.

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

webpack 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).

Release Notes for v4.27.0

Features

  • When using functions as plugins they are now also called with the compiler as parameter
    • This make it possible to use arrow functions as plugins
  • splitChunks.maxSize now emits a warning when minSize > maxSize
  • Loaders have now access to a getResolve method to create their own resolver function with custom options

Bugfixes

  • splitChunks.cacheGroups.xxx.enforce now behaves as documented and enforce chunk creation
  • splitChunks.cacheGroups.xxx.enforce now no longer deletes minSize for maxSize
  • fixes a bug where splitChunks cause cacheGroups to be incorrectly merged when using the same name
    • now conditions are considered per cacheGroup
    • the correct cache group comment is displayed in stats
  • fixes a bug which causes providedExports not to be updated on rebuilds when using export * from
Commits

The new version differs by 12 commits.

  • f47bf8b 4.27.0
  • a67ffcd Merge pull request #8452 from webpack/feature/resolveWithOptions
  • 96f625c Merge pull request #8457 from webpack/bugfix/rebuild-provided-exports
  • 56feccc convert test case to normal function for node.js 6 support
  • 2f4296e fix a bug which causes incorrect providedExports for cached modules
  • f944002 Merge pull request #8451 from webpack/bugfix/split-chunks
  • 162da1c add getResolve method to loader context
  • 3b46b48 enforce doesn't affect minSize for maxSize
  • 72a8a1f Merge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated
  • 537d3e4 Cache hasRunstime in chunk
  • e3e8a68 Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply
  • 70b9a1b fix parameter missing when plugin type is a funtion

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 ๐ŸŒด

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.