Node 16 is now EOL and GitHub actions that use this runtime will start showing warnings from Octopus 2023. We'll want to upgrade this action to use node 20.

Describe the bug
Using v1.1.10 of this action, passing latest into the version input is still getting v7.4.3663 of the cli.
Latest seems to be v9.0.0 per octopus.com/downloads

To Reproduce
Use the following:

      - name: Install Octopus CLI
        uses: OctopusDeploy/[email protected]
        with:
          version: latest

Expected behavior
Version 9.0.0 should be downloaded, installed, and used

Screenshots

Additional context
This is running on a self-hosted Windows Server 2019 machine.
Looks like there is a .json file living at https://download.octopusdeploy.com/octopus-tools/latest.json that is still referencing v7.4.3663

I'm not sure where that file is located or I would see about making a PR to update it.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @vercel/ncc to v0.38.1
• fix(deps): update dependency @actions/http-client to v2.2.1

Detected dependencies

Hi, I'm using the latest Octopus step (1.1.9) and I'm getting the error:

Cannot convert argument "entryNameEncoding", with value: "True", for "ExtractToDirectory" to type "System.Text.Encoding": "Cannot convert value "True" to type "System.Text.Encoding". Error: "Invalid cast from 'System.Boolean' to 'System.Text.Encoding'.""

Error: Error: The process 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' failed with exit code 1

To Reproduce

Use the following:

  - name: Install Octopus CLI
    uses: OctopusDeploy/[email protected]
    with:
      version: latest

We are using a self-hosted runner, sadly on Window server 2012 R2

Screenshots

Describe the bug
Octopus CLI is not able to install in GHA.

To Reproduce
Steps to reproduce the behavior:
Try to install octopus cli in GHA.

Expected behavior
It should install.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser Edge

Additional context
I think the problem is at: https://github.com/OctopusDeploy/install-octopus-cli-action/blob/main/src/octopus-cli.ts#L60 where the file is downloaded and parsed. It looks like a version field is expected which seems to be missing from the file.

This action may occasionally encounter a challenge by a reverse proxy (i.e. Cloudflare) that fronts the download location for the Octopus CLI. This creates downstream errors in workflows.

Example: https://github.com/OctopusDeploy/create-release-action/runs/7137962623?check_suite_focus=true

Our new short-link service (using short.io) under the https://oc.to/ domain (rather than g.octopushq.com) should go-live by May EOM. We need to switch over this once it's available.

• ensure to use the NuGet package feed; not the JSON feed that we publish

v2 of the CodeQL action is being deprecated, we should look to upgrade to v3.

Describe the bug
Failed to install latest Octopus CLI

To Reproduce
Workflow

      - name: Install Octopus CLI
        uses: OctopusDeploy/[email protected]
        with:
          version: latest

Fails to execute with the following error:
Expand-Archive : is not a supported archive file format. .zip is the only supported archive file format.

Expected behavior
Installation of Octopus CLI should be successful

Screenshots

Desktop (please complete the following information):

• OS: Windows self-hosted runner

Add automated dependency management to this action using dependabot or similar.

I have spent quite a bit of time via trial and error to update to this new version.

For example:

• command is no longer 'octo' but is now 'octopus'
• command pack is no longer even an option?

It appears this is no really 'ready' as there are no docs on the new GO CLI and no docs on converting. I think this should have been released as a beta or something.

For now, I have rolled back to the 1.x versions to get it to work. Please advise on the desired path users should go.

Describe the bug
getting error message: Octopus CLI version not found: 1.7.1 when running install octopus CLI action on self-hosted linux runner

To Reproduce
Use the install octopus CLI action in a github action

Expected behavior
The latest Octopus CLI should install

Screenshots

Additional context
Self hosted Linux Runner

Hello, thanks for the convenient action! Unfortunately it is outdated, because it still uses the node12 runtime, can you please update to use node16?

@johnsimons @matt-richardson

We have Dependabot security alerts enabled on this repo, however have found that notifications for these can lost amongst the noise. We'd like to create a specific workflow that runs regularly to send a slack notification to the right channel to alert the team of any pending alerts so they can be actioned.

Describe the bug
Related to #139.

I'm using the latest Octopus step (1.1.8) and I'm still getting the error:

Expand-Archive : is not a supported archive file format. .zip is the only supported archive file format.

To Reproduce
Use the following:

      - name: Install Octopus CLI
        uses: OctopusDeploy/[email protected]
        with:
          version: latest

Expected behavior
Installation of Octopus CLI should be successful

Screenshots

Powershell Version:

5.1.17763.2268

Describe the bug
When using this action often, we intermittently get an error message about API throttling. We are not using this maliciously at all and the rate at which we build should be within the API limits.

Error: HttpClientError: API rate limit exceeded for #.#.#.#. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

To Reproduce
Steps to reproduce the behavior:

1. Use action enough to hit limit (not sure how often that is)

Expected behavior
I expect that the API call will not be rate limited.

Screenshots

Additional context
While looking through the code for the action it looks like it uses the github api to get the latest release. I don't see how it's sending any authentication which, according to the error message, may increase the api limits.

https://github.com/OctopusDeploy/install-octopus-cli-action/blob/main/src/octopus-cli.ts

18  const releasesUrl = `https://api.github.com/repos/OctopusDeploy/cli/releases
...
59  const releasesResponse = (await http.getJson<GitHubRelease[]>(releasesUrl)).result