Update balena-request to v11.4.2

[klutchell]

Update balena-request from 11.4.1 to 11.4.2

Change-type: patch
Signed-off-by: Kyle Harding kyle@balena.io

---

Contributor checklist

• Includes tests
• Includes typings
• Includes updated documentation
• Includes updated build output

[klutchell]

@balena-ci I self-certify!

[klutchell]

@balena-ci retest

[thgreasi]

@klutchell I restarted the tests from appveyor (balena-ci retest doesn't do that).

FAILED TESTS:
  Logs
    given a device
      balena.logs.history()
        ✖ should successfully load historical logs
          HeadlessChrome 79.0.3945 (Windows 8.1.0.0)
        O: Request error: The API cannot handle your request right now
            at Object.<anonymous> (es2015/balena-browser.min.js:1:121658)
            at Generator.next (<anonymous>)
            at n (es2015/balena-browser.min.js:1:503680)

Looks like it's related to what was reported at:
See: https://www.flowdock.com/app/rulemotion/resin-devops/threads/vRYzOsq21lcYUHQFIX42_x1DxQc

[klutchell]

Looks like it's related to what was reported at

@thgreasi thanks, that's what I suspected as well with the API timeouts

[thgreasi]

The node tests atm fail b/c of
See: node-fetch/node-fetch#1300

[LinusU]

The node-fetch bug was fixed in 2.6.4, sorry for any inconvenience!

[klutchell]

@thgreasi I think we are getting node-fetch from here: https://www.npmjs.com/package/fetch-ponyfill?activeTab=explore

How do we normally bump a dependency independently of an upstream that requires it? Just require the specified version of node-fetch in balena-request directly?

[LinusU]

Since you don't have a package lock file I think that you can just rerun the jobs and they should pick up the new version 🚀

[thgreasi]

Thanks for the new release heads-up @LinusU. I'm honored 🙏