#271: Update npm-publish-action to latest version

[swgnr]

Hi!

I saw that that there's currently an issue going on with publishing the package to npm in #271. It seems that a recent git update now checks whether the folder into which a repo is cloned is owned by the same user running the 'git' executable for security purposes.

A fix has already been merged in npm-publish-action some while ago (see: pascalgn/npm-publish-action#42). This PR would update the version of the plugin to the latest stable release.

With any luck, those should be the only changes needed.

Thanks for keeping noble alive! :)

[donavanbecker]

@rzr

[swgnr]

Just as an addendum: This will not fix the Win32 build actions. It looks like the CI pipeline is still using the windows-2016 image which has been phased out by GitHub earlier this year (see actions/runner-images#4312).

I saw that there have already been attempts at upgrading the Windows image earlier (see: 56c46b2), but those changes got reverted.

Trying to further look into this, though I'm not really familiar with Windows development stuff.

[codecov-commenter]

Codecov Report

Merging #272 (87af9cf) into master (057f69f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #272   +/-   ##
=======================================
  Coverage   93.80%   93.80%           
=======================================
  Files          23       23           
  Lines        2856     2856           
=======================================
  Hits         2679     2679           
  Misses        177      177           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.