Compare commits

..

9 Commits

Author SHA1 Message Date
Priya Gupta
06cec21687 Test macos-14-large runner 2025-07-25 13:43:17 +05:30
Ben De St Paer-Gotch
552a1a5fda Merge pull request #86 from actions/nebuk89-patch-1
Update README.md
2025-06-12 10:28:55 +01:00
Ben De St Paer-Gotch
1e5d44c7a5 Update README.md 2025-06-06 11:58:24 +01:00
HarithaVattikuti
817eacd539 Create dependabot.yml (#83) 2025-01-23 09:37:14 -06:00
HarithaVattikuti
933aacb90a Add permission section (#84) 2025-01-16 08:45:16 -06:00
HarithaVattikuti
d3c3feee4b Point to ubuntu-22.04 (#82) 2025-01-08 22:43:01 -06:00
Priya Gupta
4028baf988 Replace deprecated release action with GitHub CLI (#80) 2024-11-12 21:15:45 -06:00
aparnajyothi-y
d30950623a Upgrade the checkout to V4 (#79)
* Update versions to latest

* Update create-pr-to-update-manifest.yml

* Update get-new-tool-versions.yml

* Update get-tools-new-versions.yml

* Update validate-manifest.yml
2024-11-12 21:11:54 -06:00
gowridurgad
16b7940fde Add test jobs for arm64 architecture (#76)
* Update build-tool-packages.yml

* Update build-tool-packages.yml

* Update build-tool-packages.yml

* added RUNNER_TYPE

---------

Co-authored-by: aparnajyothi-y <147696841+aparnajyothi-y@users.noreply.github.com>
Co-authored-by: gowridurgad <gowridurga@github.com>
2024-07-09 09:46:50 -05:00
8 changed files with 66 additions and 24 deletions

14
.github/dependabot.yml vendored Normal file
View File

@@ -0,0 +1,14 @@
# 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'

View File

@@ -30,7 +30,7 @@ jobs:
build:
name: Build ${{ inputs.tool-name }} ${{ inputs.tool-version }} [${{ matrix.platform }}] [${{ matrix.architecture }}]
runs-on: ubuntu-latest
runs-on: ubuntu-22.04
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') }}
@@ -76,7 +76,7 @@ jobs:
- os: ubuntu-latest
platform: linux
architecture: x64
- os: macos-13
- os: macos-14-large
platform: darwin
architecture: x64
- os: windows-latest
@@ -86,7 +86,7 @@ jobs:
platform: linux
architecture: arm64
runner_type: self-hosted
- os: macos-latest
- os: macos-15
platform: darwin
architecture: arm64
- os: setup-actions-windows-arm64-4-core
@@ -215,14 +215,18 @@ jobs:
- name: Publish Release
id: create_release
uses: actions/create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag_name: ${{ inputs.tool-version }}-${{ github.run_id }}
release_name: ${{ inputs.tool-version }}
body: |
${{ steps.generate-release-body.outputs.RELEASE_BODY }}
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
shell: bash
run: |
tag_name="${{ inputs.tool-version }}-${{ github.run_id }}"
gh release create "$tag_name" \
--repo="$GITHUB_REPOSITORY" \
--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: |

View File

@@ -7,7 +7,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
uses: actions/checkout@v4
- name: Install Pester
shell: pwsh
@@ -20,4 +20,4 @@ jobs:
run: |
Import-Module Pester
Import-Module Assert
Invoke-Pester -EnableExit
Invoke-Pester -EnableExit

View File

@@ -20,7 +20,7 @@ jobs:
name: Create Pull Request
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4
with:
submodules: true
@@ -40,4 +40,4 @@ jobs:
-BranchName "update-versions-manifest-file" `
-CommitMessage "Update versions-manifest" `
-PullRequestTitle "[versions-manifest] Update for release from ${formattedDate}" `
-PullRequestBody "Update versions-manifest.json for release from ${formattedDate}"
-PullRequestBody "Update versions-manifest.json for release from ${formattedDate}"

View File

@@ -30,7 +30,7 @@ jobs:
outputs:
versions_output: ${{ steps.Get_new_versions.outputs.TOOL_VERSIONS }}
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4
with:
submodules: true
@@ -45,7 +45,7 @@ jobs:
env:
TOOL_VERSIONS: ${{needs.find_new_versions.outputs.versions_output}}
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4
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@v3
- uses: actions/checkout@v4
with:
submodules: true
@@ -95,7 +95,7 @@ jobs:
needs: [find_new_versions, check_new_versions, trigger_builds]
if: failure()
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4
with:
submodules: true

View File

@@ -42,7 +42,7 @@ jobs:
name: 'Searching for new versions of ${{ matrix.tool.name }}'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4
- 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@v2
- uses: actions/checkout@v4
- id: get-failed-jobs
name: Get failed jobs
run: |

View File

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

View File

@@ -1,5 +1,29 @@
# 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
## Contribution
Contributions are welcome! See [Contributor's Guide](./CONTRIBUTING.md) for more details about contribution process and code structure
## Recommended permissions
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 were working on and what stage theyre 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.