actions: Error: Cannot read property 'trim' of undefined

Surprisingly, this action which used to work started to fail today, using v1.1.0 (using sha).

Generating changelog
  Found 1 pull request(s) associated with commit 234cefd9e510cd6db5ef9d1d9bed6f882d8b2363
  Error: Cannot read property 'trim' of undefined
  (node:2477) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'trim' of undefined
      at e.exports (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:562792)
      at Function.e.exports.sync (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:561270)
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:211488
      at Generator.next (<anonymous>)
      at s (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:210383)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
  (node:2477) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:2477) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

image

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 21 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@Vadorequest To be clear, I didn’t mean rebasing this repo. I mean rebasing your own repo so that merge commits have more than one line of non-empty text.

I think so.