chore(rsc-runtime): drop the react-server-components keyword (#106) #65

	name: Release packages

	on:
	push:
	branches:
	- main

	# id-token is required for npm package provenance once publishing starts; it is
	# inert while the NPM_TOKEN gate below keeps the publish steps skipped.
	permissions:
	contents: write
	id-token: write
	pull-requests: write

	concurrency:
	group: package-release

	jobs:
	release:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v7
	# No npm release is cut yet; skip publishing until an NPM_TOKEN secret
	# exists instead of failing every push to main. Previews stay on
	# pkg.pr.new (docs/preview-packages.md).
	- id: gate
	env:
	NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
	run: echo "enabled=${{ env.NPM_TOKEN != '' }}" >> "$GITHUB_OUTPUT"
	- if: steps.gate.outputs.enabled == 'true'
	uses: pnpm/setup@v2
	with:
	cache: true
	install: false
	runtime: node@22.19.0
	- if: steps.gate.outputs.enabled == 'true'
	run: pnpm install --frozen-lockfile
	# changesets/action v2 no longer writes .npmrc from an NPM_TOKEN env
	# variable; expose the token via npm config so `changeset publish`
	# (pnpm publish) can authenticate. The ${NPM_TOKEN} placeholder is kept
	# literal here and expanded by npm/pnpm from the step environment.
	- if: steps.gate.outputs.enabled == 'true'
	run: echo '//registry.npmjs.org/:_authToken=${NPM_TOKEN}' >> "$HOME/.npmrc"
	- if: steps.gate.outputs.enabled == 'true'
	uses: changesets/action@v2
	with:
	publish-script: pnpm release
	version-script: pnpm version-packages
	github-token: ${{ secrets.GITHUB_TOKEN }}
	env:
	NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

Navigation Menu