lgaticaq / bip Goto Github PK

Version 9.0.9 of nock just got published.

Branch	Build failing 🚨
Dependency	nock
Current Version	9.0.8
Type	devDependency

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

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

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

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 4 commits .

• 5b1a8d8 9.0.9: Revert PR #802
• 51809e1 Merge pull request #840 from node-nock/revert-802-fix-754
• 0a083f6 Revert "Fix request timeout no working"
• 3728a1f Changelog v9.0.8

See the full diff.

Not sure how things should work exactly?

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

---

Your Greenkeeper Bot 🌴

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency eslint-plugin-standard to v5
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency mocha to v10
• chore(deps): update dependency node to v20
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency cheerio to v1.0.0-rc.12
• chore(deps): update dependency chai to v4.4.1
• chore(deps): update dependency eslint-plugin-import to v2.29.1
• chore(deps): update dependency chai to v5
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-standard to v17
• chore(deps): update dependency eslint-plugin-node to v11
• chore(deps): update dependency eslint-plugin-promise to v6
• chore(deps): update dependency nock to v13
• chore(deps): update dependency prettier-standard to v16
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

npm

package.json

• cheerio 1.0.0-rc.3
• chai 4.3.6
• eslint 5.16.0
• eslint-config-standard 11.0.0
• eslint-plugin-import 2.27.5
• eslint-plugin-node 7.0.1
• eslint-plugin-promise 3.8.0
• eslint-plugin-standard 4.1.0
• generate-changelog 1.8.0
• husky 0.14.3
• istanbul 1.1.0-alpha.1
• lint-staged 7.3.0
• mocha 5.2.0
• nock 9.6.1
• prettier-standard 8.0.1
• node >=8

nvm

.nvmrc

• node v9

travis

.travis.yml

• node 8
• node 9

---

• Check this box to trigger a request for Renovate to run again on this repository

When I use psep.cl's endpoint (http://www.psep.cl/api/Bip.php?&numberBip=22261566), it returns the date, but when I try to ask for the same BIP! Card number using this lib, it show me "Invalid date"

Note: I was following the documentation (https://github.com/lgaticaq/bip#use)

Version 1.2.0 of generate-changelog just got published.

Branch	Build failing 🚨
Dependency	generate-changelog
Current Version	1.1.0
Type	devDependency

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

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

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

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• 807e2e4 1.2.0
• 6de2399 updated CHANGELOG.md
• 7bdbe7a Merge pull request #16 from tvardy/allow-no-category
• 11fbbd9 Merge pull request #15 from tvardy/exclude
• a859a9b fix(writer): don't print category if empty
• 006a2a0 test(package): fix coverage for lib/package.js
• fc31e9a feat(exclude): add -x, --exclude option

See the full diff

Not sure how things should work exactly?

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

---

Your Greenkeeper Bot 🌴