Skip to content

chore: bump dependencies (#383) #213

chore: bump dependencies (#383)

chore: bump dependencies (#383) #213

Workflow file for this run

name: Release
# Opens / updates a "chore: release" PR when changesets are queued on main.
# Uses changesets/action with `commitMode: github-api`, so commits go through
# the GitHub REST API and are auto-signed by GitHub's signing key. This
# satisfies the "Commits must have verified signatures" repository rule
# without any GPG key management or bypass exceptions.
#
# Publishing to npm is enabled via the npm Trusted Publisher mechanism.
# The workflow filename (`release.yml`) is bound to the publisher config on
# npm.com — renaming or replacing this file will break publishing until the
# npm-side setting is updated to match.
#
# See https://docs.npmjs.com/trusted-publishers for the publisher binding.
on:
push:
branches:
- main
concurrency: ${{ github.workflow }}-${{ github.ref }}
jobs:
release:
name: Release
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
id-token: write
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Setup pnpm
uses: pnpm/action-setup@v4
# Node 24 (LTS Krypton) ships npm >= 11.12, which has Trusted Publisher
# OIDC authentication. Node 22's bundled npm 10.x can sign provenance
# attestations but cannot use OIDC tokens to authenticate the publish
# itself, leading to a confusing 404 after provenance signing succeeds.
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: 24
cache: pnpm
registry-url: https://registry.npmjs.org
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Create Release Pull Request or Publish
uses: changesets/action@6a0a831ff30acef54f2c6aa1cbbc1096b066edaf # v1.7.0
with:
version: pnpm run version
publish: pnpm run release
commit: "chore: release"
title: "chore: release"
commitMode: github-api
env:
NPM_CONFIG_PROVENANCE: "true"
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}