Use crypto api import for CryptoCallbacks
instead of legacy crypto
#3631
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: Backport | |
on: | |
pull_request_target: | |
types: | |
- closed | |
- labeled | |
branches: | |
- develop | |
jobs: | |
backport: | |
name: Backport | |
runs-on: ubuntu-24.04 | |
# Only react to merged PRs for security reasons. | |
# See https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target. | |
if: > | |
github.event.pull_request.merged | |
&& ( | |
github.event.action == 'closed' | |
|| ( | |
github.event.action == 'labeled' | |
&& contains(github.event.label.name, 'backport') | |
) | |
) | |
steps: | |
- uses: tibdex/backport@9565281eda0731b1d20c4025c43339fb0a23812e # v2 | |
with: | |
labels_template: "<%= JSON.stringify([...labels, 'X-Release-Blocker']) %>" | |
# We can't use GITHUB_TOKEN here or CI won't run on the new PR | |
github_token: ${{ secrets.ELEMENT_BOT_TOKEN }} |