setup-processing

Sets up the Processing SDK. Given a tag name and a release asset name, setup-processing will try to download a release asset from Processing 4 or Processing.

Note

• 🚨🚨🚨 Please note that this action DOES NOT work with processing revision 1300 or newer (i.e., >=4.4.0)🚨🚨🚨
  • This is because installation files of these revisions do not follow folder structure conventions of previous revisions. Supporting installation of these versions would significantly complicate this GH action.
  • Please use their MSI / DMG / snap installer instead for installing processing. Check out the attached files of a processing release, e.g., the release page for 4.4.0.
• If no tag name tag is provided, the latest release will be used.
• If no asset name asset-name is provided, this action will try to choose the right asset based on the Action Runner's OS and CPU architecture.
• This action uses github.token to extend the GitHub release fetching rate limit. You may change the used token with the Action input token

Usage

Check these example workflows.

Example

Check this action.yaml for more information.

- name: Setup Processing
  id: setup-processing
  uses: pr1metine/[email protected]
  with:
    # Tag of Processing GitHub Release, e.g. processing-1292-4.2
    # See https://github.com/processing/processing4/releases and
    # https://github.com/processing/processing4/releases
    tag: "processing-1292-4.2" # optional, will use latest release by default
    # Name of a Processing GitHub Release Asset, e.g. processing-4.2-linux-arm64.tgz
    asset-name: "processing-4.2-linux-x64.tgz" # optional, will infer based on Runner by default
- name: Output Processing installation directory
  run: echo "${{steps.setup-processing.outputs.install-dir}}"

Development

• I currently use Node v20.4.0
• This file serves as this Action's entry point.
• Use act to test this GitHub Action locally before pushing.