v1.22.2 has breaking change with the strictness of "onOperation" for what is a valid answer

[jeremiewtd]

Using v1.22.1, returning this value from the onOperation handler works well but now doesn't work anymore using the v1.22.2 :

return [
  JSON.stringify(result),
  {
    status: 200,
    headers: {
      'content-type': 'application/json; charset=utf-8',
    },
  },
];

Looking at the code in this PR, this should be the source of the changes, the validation of type of statusText introduces a breaking change of the interpretation of what is returned by onOperation.

The example above doesn't work anymore, maybe this code is not suitable from the beginning but with v1.22.1 it worked.

Expected Behaviour
The given response still works or else the library should have change its major version.

Actual Behaviour
The given response is not interpreted as a valid response anymore.

Further Information
A bit surprising that this change (and others) are not included in the changelog for this release.

[enisdenjo]

Thanks for pointing this out, this was an oversight on my end. Both status and statusText are actually optional (see here).

I'll roll out a fix soon!

[enisdenjo]

🎉 This issue has been resolved in version 1.22.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀