Merge pull request #6 from actions/pje/upgrade-upload-artifact-to-v4

Upgrade actions/upload-artifact to v4

.github/workflows/build-release-alpine-nodejs.yml

@@ -32,7 +32,7 @@ jobs:
          docker run --rm -v $RUNNER_TEMP/alpine_node:/node_output alpine_nodejs:${{github.event.inputs.NodeVersion}}
          ls -l -R $RUNNER_TEMP/alpine_node
     - name: Upload alpine node.js
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       with:
         name: alpine_nodejs_${{github.event.inputs.NodeVersion}}
         path:  ${{runner.temp}}/alpine_node/node-${{github.event.inputs.NodeVersion}}-alpine-x64.tar.gz
@@ -44,7 +44,7 @@ jobs:
     container: alpine
     steps:
     - name: Download alpine node.js
-      uses: actions/download-artifact@v3
+      uses: actions/download-artifact@v4
       with:
         name: alpine_nodejs_${{github.event.inputs.NodeVersion}}
     - run: |
@@ -62,7 +62,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Download alpine node.js
-      uses: actions/download-artifact@v3
+      uses: actions/download-artifact@v4
       with:
         name: alpine_nodejs_${{github.event.inputs.NodeVersion}}
     # Create GitHub release

CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# Contributing
+
+## Submitting a pull request
+
+1. Fork and clone the repository
+1. Create a new branch: `git checkout -b my-branch-name`
+1. Push to your fork and submit a pull request
+1. Pat yourself on the back and wait for your pull request to be reviewed and merged
+
+## Tips for working this repository:  
+> - The repository is huge right now, you don't want to waste your time and disk space to get those unrelated files.
+>   - Ignore LFS files during initial `git clone` the repo with `GIT_LFS_SKIP_SMUDGE=1 git clone https://mseng@dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals`
+>   - Ignore LFS files during any `git checkout` or `git fetch` operation with `GIT_LFS_SKIP_SMUDGE=1`.
+>   - You do want the LFS smudge filter to run during `git add` and `git push`, make sure you don't have `GIT_LFS_SKIP_SMUDGE=1` when you run `git add` and `git push`.
+> - More `Git-LFS` doc is at https://github.com/git-lfs/git-lfs/tree/main/docs
+
+Thanks! :heart: :heart: :heart:
+
+GitHub Actions Team :octocat:

README.md

@@ -1,8 +1,11 @@
-# alpine_nodejs
+# GitHub Alpine NodeJS
 
-[GitHub Actions Runner](https://github.com/actions/runner/blob/main/src/Misc/externals.sh) download alpine node.js from https://vstsagenttools.blob.core.windows.net/tools/nodejs
+[![Actions Status](https://github.com/actions/alpine_nodejs/workflows/Build%20Alpine%20Node.js/badge.svg)](https://github.com/actions/alpine_nodejs/actions)
 
-The [workflow](https://github.com/TingluoHuang/alpine_nodejs/actions/workflows/docker-image.yml) in this repository can compile a partial-static node.js for alpine and create a [GitHub release](https://github.com/TingluoHuang/alpine_nodejs/releases) for it.
+The Alpine NodeJS repo houses a redistribution of NodeJS builds that are used within the [GitHub Actions Runner](https://github.com/actions/runner/blob/main/src/Misc/externals.sh).
+
+## Getting Started
+The [workflow](https://github.com/actions/alpine_nodejs/actions/workflows/docker-image.yml) in this repository can compile a partial-static node.js for alpine and create a [GitHub release](https://github.com/actions/alpine_nodejs/releases) for it.
 
 - Queue workflow using `workflow_dispatch` trigger and set the `node` version you want to compile as input, ex: `v12.22.7`
 ![queue workflow](./res/queueWorkflow.png)
@@ -13,10 +16,3 @@ The [workflow](https://github.com/TingluoHuang/alpine_nodejs/actions/workflows/d
 - There should be a newly created release that matches the version you want for `node`, and it is able to run on alpine.
 ![new release](./res/createdRelease.png)
 
-- Once we get [approval](https://github.com/github/open-source-releases/issues/205) to change the current repository from `private` to `public`, then we can consume the release assets directly. In the meantime, you will need to follow [instructions](https://dev.azure.com/mseng/AzureDevOps/_wiki/wikis/AzureDevOps.wiki/4037/How-to-upload-resource-to-vstsagenttools.blob.core.windows.net) to check-in the compiled alpine node.js from the release assets as a `Git-LFS` files to https://dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals and get it mirror into https://vstsagenttools.blob.core.windows.net/tools/nodejs
-> Tips for working with `CIPlat.Externals` repository:  
-> - The repository is huge right now, you don't want to waste your time and disk space to get those unrelated files.
->   - Ignore LFS files during initial `git clone` the repo with `GIT_LFS_SKIP_SMUDGE=1 git clone https://mseng@dev.azure.com/mseng/AzureDevOps/_git/CIPlat.Externals`
->   - Ignore LFS files during any `git checkout` or `git fetch` operation with `GIT_LFS_SKIP_SMUDGE=1`.
->   - You do want the LFS smudge filter to run during `git add` and `git push`, make sure you don't have `GIT_LFS_SKIP_SMUDGE=1` when you run `git add` and `git push`.
-> - More `Git-LFS` doc is at https://github.com/git-lfs/git-lfs/tree/main/docs

SUPPORT.md

@@ -0,0 +1,12 @@
+
+# Support 
+
+## How to file issues and get help
+
+This project does not support issues, however you may submit a pull request with any proposed improvements.
+
+`actions/alpine_nodejs` is under active development and maintained by GitHub staff **AND THE COMMUNITY**. We will do our best to respond to support, feature requests, and community questions in a timely manner.
+
+## GitHub Support Policy
+
+Support for this project is limited to the resources listed above.