v3.2.5 - Properly set action version when starting a Rainforest run

🛠️ Fixes

• Fix setting of version when starting a run (#38)

Full Changelog: v3.2.4...v3.2.5

v3.2.4 - Update README

🛠️ Fixes

No functional changes are present in this release.

v3.2.3 - Handle quotes in branch, description, and release inputs

🛠️ Fixes

Properly handle " characters in the branch, description, and release inputs.

This was originally released as v3.2.1 which had to be reverted.

v3.2.2 - This is the same as v3.2.0

v3.2.1 was a broken release. This release is a revert back to v3.2.0

v3.2.0 - Support triggering multiple runs from a single workflow using a reusable workflow

🛠️ Fixes

This release adds a new optional cache_key parameter to support triggering multiple runs through a reusable workflow via workflow_dispatch.

The Rainforest QA GitHub Action cannot detect on its own when it is being called multiple times in a single workflow through an intermediary reusable workflow. This means that the second invocation will attempt to rerun the run created by the first invocation, which will fail if that run has no failed tests to rerun. In order to avoid this situation, set the cache_key parameter to a distinct value in each invocation:

# reusable workflow
on:
  worklow_call:
    inputs:
      cache_key:
        type: string

jobs:
  rainforest:
    runs-on: ubuntu-latest
    name: Run Rainforest
    steps:
      - name: Rainforest
        uses: rainforestapp/github-action@master
        with:
          token: ${{ secrets.RAINFOREST_API_TOKEN }}
          run_group_id: 1234
          cache_key: ${{ inputs.cache_key }}

# calling workflow
jobs:
  first-invocation:
    uses: ./.github/workflows/reusable.yml
    with:
      cache_key: first-invocation

  second-invocation:
    uses: ./.github/workflows/reusable.yml
    with:
      cache_key: second-invocation

v3.1.0 Add Rainforest branching support

🆕 Features

This release adds a new branch parameter, which maps to the Rainforest CLI's --branch flag.

v3.0.0 - Update dependencies to use node16 runtime

🛠️ Updates

This release upgrades our dependencies to versions running their steps on Node 16 rather than on deprecated Node 12. This could potentially be a breaking change for some users:

This change adds a minimum runner version(node12 -> node16), which can break users using an out-of-date/fork of the runner. This would be most commonly affecting users on GHES 3.3 or before, as those runners do not support node16 actions and they can use actions from github.com via github connect or manually copying the repo to their GHES instance.

v2.2.1 - Support multiple runs in a repository

🛠️ Fixes

With this release, rerunning failed workflows will work even if multiple runs are triggered via the Rainforest QA GitHub Action in a single repository, whether in the same workflow or in multiple workflows.

v2.2.0 - Add automation_max_retries

🆕 Features

This release adds a new automation_max_retries parameter, which maps to the Rainforest CLI's --automation-max-retries flag.

v2.1.0 - Add execution_method, deprecate crowd

Deprecations / Replacements

A new execution_method parameter replaces the now-deprecated crowd parameter. You may not use both parameters together. If neither parameter is set the run will use the Run Group's execution method.

What	Then	Now
Running tests using the Tester Community	crowd: default	execution_method: crowd
Running tests using the Automation Service	crowd: automation	execution_method: automation
Running automatable tests using the Automation Service and non-automatable tests using the Tester Community	crowd: automation_and_crowd	execution_method: automation_and_crowd
Running tests using your On-Prem testers	crowd: on_premise_crowd	execution_method: on_premise