Skip to content

chore(deps): bump pyjwt from 2.13.0 to 2.15.0 in /python/neutron-understack #792

chore(deps): bump pyjwt from 2.13.0 to 2.15.0 in /python/neutron-understack

chore(deps): bump pyjwt from 2.13.0 to 2.15.0 in /python/neutron-understack #792

Workflow file for this run

name: Labeler

Check warning on line 1 in .github/workflows/labeler.yaml

View workflow run for this annotation

GitHub Actions / Labeler

Workflow execution policy warning (evaluate mode)

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
# Applies the path-derived labels in .github/labeler.yml so that
# .github/release.yml can keep separately released changes out of the platform
# release notes.
#
# Uses pull_request_target because a pull_request run from a fork gets a
# read-only token and cannot label anything. That trigger runs the workflow
# definition from the base branch with a writable token, which is only safe
# because nothing here checks out or executes the pull request's code --
# actions/labeler works entirely from the API. Do not add a checkout step.
on:
pull_request_target:
types: [opened, synchronize, reopened]
permissions: {}
concurrency:
group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
label:
name: Apply path labels
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write
steps:
- uses: actions/labeler@bf12e9b00b37c5c0ca2b87b79b2daf7891dbda13 # v7.0.0
with:
# Remove the label again when a pull request grows beyond the
# separately released subtree. Without this, adding a chart change to
# an understackctl pull request would leave it excluded from the
# release notes.
sync-labels: true