[MacPorts] #72492: got: update to 0.112

[MacPorts]

#72492: got: update to 0.112
-----------------------+----------------------
  Reporter:  artkiver  |      Owner:  artkiver
      Type:  update    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  haspatch
      Port:  got       |
-----------------------+----------------------

Comment (by mascguy):

 Replying to [comment:1 ryandesign]:
 > If the build succeeds on your system but is known to fail on GitHub
 Actions because they block access from those IPs, just say so in the PR
 and it can be merged ignoring the GitHub Actions failure.

 That idea makes me a tad uncomfortable: Given the continuing rise of
 malware, etc, the last thing we should do is merge a PR without knowing
 what the payload is. That also bypasses some helpful security scans that
 GitHub runs.

 Granted, when it is from someone we know, that reduces the chance of it
 occurring. Even still, I wouldn't be comfortable merging PR's where the
 dist files can't be pulled.

 Ryan, can you manually mirror the distfile, for such a (hopefully very
 rare) case like this? That would be far more palatable than blindly
 merging a PR.

 Thoughts?

-- 
Ticket URL: <https://trac.macports.org/ticket/72492#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS