Update to `node20`

This release updates the action to run on Node.js v20. When you're running on GitHub hosted runners, just go ahead and update. When you're using self-hosted runners, please make sure you have Node.js v20 installed before updating from v0.8.0 to v0.9.0 of this action.

New Contributors

• @npwolf made their first contribution in #196
• @benzado made their first contribution in #206
• @felix-seifert made their first contribution in #199
• @archen made their first contribution in #201

Full Changelog: v0.8.0...v0.9.0

What's Changed

• Update README.md to reflect latest version by @npwolf in #196
• Remove outdated claim from README by @benzado in #206
• chore: update all versions of actions/checkout to v4 by @felix-seifert in #199
• bump to node20 by @archen in #201

New Contributors

• @npwolf made their first contribution in #196
• @benzado made their first contribution in #206
• @felix-seifert made their first contribution in #199
• @archen made their first contribution in #201

Full Changelog: v0.8.0...v0.9.0

SSH host keys no longer managed – read below 👇

Starting with this release, this action no longer writes GitHub's SSH host keys into the known_hosts SSH config file upon start.

GitHub changed their host keys on short notice this morning, see https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/. We took this as an opportunity to stop maintaining GH SSH keys in the code shipped with this action (#171).

What you need to do:

• On GitHub hosted runners, nothing. ✔︎ These runners ship with SSH host keys (for github.com) maintained by directly by GitHub.
• On self-hosted runners, review and fix your SSH known_hosts file:
  • First, you'll find it bloated with redundant entries for github.com, as described in #106. Remove these entries.
  • Review https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/. You probably removed the old (invalid) SSH key in the previous step.
  • Configure GitHub's current SSH keys as documented on https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints
  • As long as versions before v0.8.0 of this action here are run on the self-hosted runner, the old entries will come back. Keep an eye on it, possibly you'll have to rinse & repeat.

Other code changes in this release

• Update to actions/checkout@v3 by @mpdude in #143
• Allow the user to override the commands for git, ssh-agent, and ssh-add by @DilumAluthge in #154

New Contributors

• @prhiggins made their first contribution in #153
• @kjarkur made their first contribution in #147
• @DilumAluthge made their first contribution in #154

Full Changelog: v0.7.0...v0.8.0

Fix Windows runners, add flag to disable logging key identities

Being the second release today, this version adds a new action input to turn off logging public key identities (#122). Additionally, Windows-based runners should work again (#137, #140) and a nonsensical log message that confused many users was fixed (#139).

Thanks to everyone involved!

New Contributors

• @ochococo made their first contribution in #137
• @j-riebe made their first contribution in #133
• @camilo-celis made their first contribution in #122

Full Changelog: v0.6.0...v0.7.0

Upgrade from Node v12 to v16

The main change in this release is that it updates from using Node v12 to Node v16. This addresses a deprecation notice / phase-out of Node v12 in GitHub Actions. See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/).

What's Changed

• Fix a typo in README.md by @koshieguchi in #109
• Bump @actions/core from 1.2.6 to 1.9.1 by @dependabot in #125
• readme: fix link to issue by @dwalkes in #120
• Update node from node12 to node16 by @bigearsenal in #132

New Contributors

• @koshieguchi made their first contribution in #109
• @dependabot made their first contribution in #125
• @dwalkes made their first contribution in #120
• @bigearsenal made their first contribution in #132

Full Changelog: v0.5.4...v0.6.0

Update GitHub Host Keys

The most important change in this release is the update of the SSH Host Keys used by GitHub.com (#102, #101).

In case you'd like to verify the keys, see https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.

Fixes for the post-action run "cleanup" phase

This release makes sure that the ssh-agent is actually terminated after workflow runs, and that this also happens on workflow failure.

Use case-insensitive scanning for deploy key repo URLs

Fixes that repository URLs (for deploy keys) were only recognized when written in lower case.

Fixes deployment keys on Windows

This release switches to using the ssh-agent and ssh-add binaries provided with Git for Windows (#63). These versions of the SSH binaries are based on a newer version of OpenSSH than the versions included in Windows natively. Deploy key support is not possible with the native versions.

Add support for Deployment Keys, Windows and container-based environments

This release brings a few exciting improvements 🙌🏻.

• The action should now support all virtual environments, including Windows and Docker-based workflows.

Of course, since this is a rather new feature, expect some rough edges and feel free to open issues for problems you encounter.

• This action now supports using multiple GitHub deployment keys

Mapping of keys to appropriate repositories happens through key comments. See the README file for more details.

Thanks 💚 to everyone involved in the discussions, for coming up with pull requests, for making suggestions and testing things.

Fix deprecated set-env command

This release addresses https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ by updating @actions/core.