extractions / netrc Goto Github PK

We ran in to an issue when running this action on the same physical machine, each time the action is invoked, the netrc info is appended to the existing netrc file, rather than replacing it. We only figured out this error when our password changed, but wasn't being picked up on the CI. Turns out our netrc file was 121K of duplicated info.

The issue is caused by the file being opened in append mode.

For example, Python's netrc module.

I need to add 2 different servers so my setup looks like this:

  - uses: extractions/netrc@v2
    with:
      machine: github.com
      username: <username>
      password: <password>
  - uses: extractions/netrc@v2
    with:
      machine: maven.pkg.github.com
      username: <username>
      password: <password>

but I believe each of these will call the post-action from #9 , and because the first call will have deleted the netrc file already, subsequent attempts fail with:

ENOENT: no such file or directory, unlink '/Users/runner/.netrc'

can you maybe add a post section to delete the file from the runner?

Hi, thanks for building this action! We have found it to be very useful

I saw that you recently made changes to update for Node 16 support (823ae2f) and I wondered if you could make a new tag release so that we could specify @2 or continue using @1? We currently are using @trunk without any issues

If a password contains characters that can be URI encoded it will be changed and stored in the .netrc file.

As an example I had a password where the first characters was % which got changed to %25