publish version 4.1.0

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Change Log
 
+## [4.1.0] - 2024-03-01
+
+-  #130 switches to use Helm published file to read latest version instead of using GitHub releases
+
 ## [4.0.0] - 2024-02-12
 
 -  #121 update to node20 as node16 is deprecated

README.md

@@ -7,15 +7,14 @@ Install a specific version of helm binary on the runner.
 Acceptable values are latest or any semantic version string like v3.5.0 Use this action in workflow to define which version of helm will be used. v2+ of this action only support Helm3.
 
 ```yaml
-- uses: azure/setup-helm@v4.0.0
+- uses: azure/setup-helm@v4.1.0
   with:
      version: '<version>' # default is latest (stable)
-     token: ${{ secrets.GITHUB_TOKEN }} # only needed if version is 'latest'
   id: install
 ```
 
 > [!NOTE]
-> When using latest version you might hit the GitHub GraphQL API hourly rate limit of 5,000. The action will then return the hardcoded default stable version (currently v3.13.3). If you rely on a certain version higher than the default, you should use that version instead of latest.
+> If something goes wrong with fetching the latest version the action will use the hardcoded default stable version (currently v3.13.3). If you rely on a certain version higher than the default, you should explicitly use that version instead of latest.
 
 The cached helm binary path is prepended to the PATH environment variable as well as stored in the helm-path output variable.
 Refer to the action metadata file for details about all the inputs https://github.com/Azure/setup-helm/blob/master/action.yml

package.json

@@ -1,6 +1,6 @@
 {
    "name": "setuphelm",
-   "version": "0.0.0",
+   "version": "4.1.0",
    "private": true,
    "description": "Setup helm",
    "author": "Anumita Shenoy",