Update webfactory/ssh-agent action to v0.9.0

[pulumi-renovate]

This PR contains the following updates:

Package	Type	Update	Change
webfactory/ssh-agent	action	minor	v0.7.0 -> v0.9.0

---

Release Notes

webfactory/ssh-agent (webfactory/ssh-agent)

v0.9.0: Update to node20

Compare Source

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 https://github.com/webfactory/ssh-agent/pull/196
• @​benzado made their first contribution in https://github.com/webfactory/ssh-agent/pull/206
• @​felix-seifert made their first contribution in https://github.com/webfactory/ssh-agent/pull/199
• @​archen made their first contribution in https://github.com/webfactory/ssh-agent/pull/201

Full Changelog: webfactory/ssh-agent@v0.8.0...v0.9.0

What's Changed

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

New Contributors

• @​npwolf made their first contribution in https://github.com/webfactory/ssh-agent/pull/196
• @​benzado made their first contribution in https://github.com/webfactory/ssh-agent/pull/206
• @​felix-seifert made their first contribution in https://github.com/webfactory/ssh-agent/pull/199
• @​archen made their first contribution in https://github.com/webfactory/ssh-agent/pull/201

Full Changelog: webfactory/ssh-agent@v0.8.0...v0.9.0

v0.8.0: SSH host keys no longer managed – read below 👇

Compare Source

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 https://github.com/webfactory/ssh-agent/pull/143
• Allow the user to override the commands for git, ssh-agent, and ssh-add by @​DilumAluthge in https://github.com/webfactory/ssh-agent/pull/154

New Contributors

• @​prhiggins made their first contribution in https://github.com/webfactory/ssh-agent/pull/153
• @​kjarkur made their first contribution in https://github.com/webfactory/ssh-agent/pull/147
• @​DilumAluthge made their first contribution in https://github.com/webfactory/ssh-agent/pull/154

Full Changelog: webfactory/ssh-agent@v0.7.0...v0.8.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[pulumi-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Command failed: make build
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
sh: 1: ts-node: not found
make[1]: *** [Makefile:25: providers] Error 127
make: *** [Makefile:4: build] Error 2

[blampe]

Closing in favor of #1176

[pulumi-renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.9.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.