added RUNNER_TYPE

.github/dependabot.yml

@@ -1,14 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
-version: 2
-updates:
-  # Enable version updates for GitHub Actions
-  - package-ecosystem: 'github-actions'
-    # Workflow files stored in the default location of `.github/workflows`
-    # You don't need to specify `/.github/workflows` for `directory`. You can use `directory: "/"`.
-    directory: '/'
-    schedule:
-      interval: 'weekly'

.github/workflows/build-tool-packages.yml

@@ -30,7 +30,7 @@ jobs:
 
   build:
     name: Build ${{ inputs.tool-name }} ${{ inputs.tool-version }} [${{ matrix.platform }}] [${{ matrix.architecture }}]
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-latest
     env: 
       ARTIFACT_NAME: ${{ inputs.tool-name }}-${{ inputs.tool-version }}-${{ matrix.platform }}-${{ matrix.architecture }}
       excludewinarm: ${{ !(inputs.tool-name == 'node' && inputs['tool-version'] < '20.0.0' && matrix.architecture == 'arm64' && matrix.platform == 'win32') }}
@@ -215,18 +215,14 @@ jobs:
 
     - name: Publish Release
       id: create_release
+      uses: actions/create-release@v1
       env:
-        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      shell: bash
+      with:
-      run: |
+        tag_name: ${{ inputs.tool-version }}-${{ github.run_id }}
-        tag_name="${{ inputs.tool-version }}-${{ github.run_id }}"
+        release_name: ${{ inputs.tool-version }}
-        gh release create "$tag_name" \
+        body: |
-          --repo="$GITHUB_REPOSITORY" \
+          ${{ steps.generate-release-body.outputs.RELEASE_BODY }}
-          --title="${{ inputs.tool-version }}" \
-          --notes="${{ steps.generate-release-body.outputs.RELEASE_BODY }}"
-          
-        release_id=$(gh release view "$tag_name" --repo "$GITHUB_REPOSITORY" --json databaseId --jq '.databaseId')
-        echo "id=$release_id" >> $GITHUB_OUTPUT
 
     - name: Generate hash for packages
       run: |

.github/workflows/common_tests.yml

@@ -7,7 +7,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Checkout
-      uses: actions/checkout@v4
+      uses: actions/checkout@v3
 
     - name: Install Pester
       shell: pwsh

.github/workflows/create-pr-to-update-manifest.yml

@@ -20,7 +20,7 @@ jobs:
     name: Create Pull Request
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v3
       with:
         submodules: true
 

.github/workflows/get-new-tool-versions.yml

@@ -30,7 +30,7 @@ jobs:
     outputs:
       versions_output: ${{ steps.Get_new_versions.outputs.TOOL_VERSIONS }}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 
@@ -45,7 +45,7 @@ jobs:
     env:
       TOOL_VERSIONS: ${{needs.find_new_versions.outputs.versions_output}}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 
@@ -75,7 +75,7 @@ jobs:
       TOOL_VERSIONS: ${{needs.find_new_versions.outputs.versions_output}}
     environment: Get Available Tools Versions - Publishing Approval
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 
@@ -95,7 +95,7 @@ jobs:
     needs: [find_new_versions, check_new_versions, trigger_builds]
     if: failure()
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 

.github/workflows/get-tools-new-versions.yml

@@ -42,7 +42,7 @@ jobs:
     name: 'Searching for new versions of ${{ matrix.tool.name }}'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
       - id: get-new-tool-versions
         name: Get new tool versions
         run: | 
@@ -71,7 +71,7 @@ jobs:
     needs: [find-new-tool-versions]
     if: failure()
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v2
       - id: get-failed-jobs
         name: Get failed jobs
         run: |

.github/workflows/validate-manifest.yml

@@ -24,7 +24,7 @@ jobs:
   validation:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 
@@ -37,7 +37,7 @@ jobs:
     needs: [validation]
     if: failure()
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           submodules: true
 

README.md

@@ -1,29 +1,5 @@
 # Common tools for generation of packages in the actions/*-versions repositories
 This repository contains PowerShell modules that are used to generate packages for Actions. The packages are consumed by the images generated through [actions/runner-images](https://github.com/actions/runner-images) and some of the setup-* Actions
 
-## Recommended permissions
+## Contribution
-
+Contributions are welcome! See [Contributor's Guide](./CONTRIBUTING.md) for more details about contribution process and code structure
-When using the `versions-package-tools` in your GitHub Actions workflow, it is recommended to set the following permissions to ensure proper functionality:
-
-```yaml
-permissions:
-  contents: read # access to read repository's content
-  actions: read # access to reading actions 
-```
-### Note
-
-Thank you for your interest in this GitHub action, however, right now we are not taking contributions. Add commentMore actionsAdd commentMore actions
-
-We continue to focus our resources on strategic areas that help our customers be successful while making developers' lives easier. While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas of Actions and are not taking contributions to this repository at this time. The GitHub public roadmap is the best place to follow along for any updates on features we’re working on and what stage they’re in.
-
-We are taking the following steps to better direct requests related to GitHub Actions, including:
-
-1. We will be directing questions and support requests to our [Community Discussions area](https://github.com/orgs/community/discussions/categories/actions)
-
-2. High Priority bugs can be reported through Community Discussions or you can report these to our support team https://support.github.com/contact/bug-report.
-
-3. Security Issues should be handled as per our [security.md](security.md)
-
-We will still provide security updates for this project and fix major breaking changes during this time.
-
-You are welcome to still raise bugs in this repo.