Skip to content

GitHub Actions: New runner release v2.267.1

We have released a new version of the GitHub Actions runner.


  • Resolve action download info from server (#508, #515, #550)
  • Print runner and machine name to log. (#539)


  • Reduce input validation warnings (#506)
  • Fix null ref exception in SecretMasker caused by hashfiles timeout. (#516)
  • Add libicu66 to ./ for Ubuntu 20.04 (#535)
  • Fix DataContract with Token service (#532)
  • Skip search $PATH on command with fully qualified path (#526)
  • Restore SELinux context on service file when SELinux is enabled (#525)
  • Fix trailing '.0' for Int64 values in ContextData (#572)


  • Remove SPS/Token migration code. Remove GHES url manipulate code. (#513)
  • Add sub-step for developer flow for clarity (#523)
  • Update Links and Language to Git + VSCode (#522)
  • Update runner configuration exception message (#540)

Learn more about GitHub Actions self-hosted runners

For questions please visit the GitHub Actions community forum

Run workflow button for workflow with workflow_dispatch

You can now create workflows that are manually triggered with the new workflow_dispatch event.
You will then see a ‘Run workflow’ button on the Actions tab, enabling you to easily trigger a run.
You can choose which branch the workflow is run on.
In addition, you can optionally specify inputs, which GitHub will present as form elements in the UI. Workflow dispatch inputs are specified with the same format as action inputs.

For example:

        description: 'Log level'     
        required: true
        default: 'warning'
        description: 'Test scenario tags'  

The triggered workflow receives the inputs in the github.event context.

For example:

    runs-on: ubuntu-latest
    - run: |
        echo "Log level: ${{ github.event.inputs.logLevel }}"
        echo "Tags: ${{ github.event.inputs.tags }}" 

If you have any questions or thoughts about these changes, we recommend asking in our GitHub Community Forum’s Actions Board!

See more

Code scanning users can now scan their code for vulnerabilities using the GitHub Open Source Static Analysis Runner (OSSAR) action.

At GitHub Satellite, we announced code scanning, part of GitHub Advanced Security. Along with showing results from CodeQL, GitHub's code analysis engine, code scanning can display findings from any static analysis tool. The OSSAR action wraps several popular open source tools to integrate them with code scanning.

If you are not yet part of the code scanning beta you can request access here.

See more