Skip to content

Fix getRequestHeaders cast against @tanstack/react-start 1.163+ typed… #21

Fix getRequestHeaders cast against @tanstack/react-start 1.163+ typed…

Fix getRequestHeaders cast against @tanstack/react-start 1.163+ typed… #21

Workflow file for this run

name: Release
on:
push:
branches:
- main
- effect-v4
concurrency: ${{ github.workflow }}-${{ github.ref }}
# Single workflow for both release lines. npm's trusted-publisher config is
# keyed on a single workflow filename, so we route everything through this
# file instead of a separate release-v4.yml.
#
# Branch-specific behavior is driven entirely by per-branch state in git:
#
# - On `main` push: no `.changeset/pre.json`, no `--tag` → `changeset publish`
# uses the `latest` npm dist-tag for 0.x (Effect v3) releases.
# - On `effect-v4` push: `.changeset/pre.json` is present (pre mode, tag =
# "beta"), so `changeset publish` automatically uses the `beta` dist-tag
# for 1.0.0-beta.N (Effect v4) releases. Passing `--tag` here would error
# ("Releasing under custom tag is not allowed in pre mode").
permissions:
contents: write
pull-requests: write
id-token: write
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: voidzero-dev/setup-vp@v1
with:
node-version: "24"
cache: true
- run: vp install
- uses: actions/setup-node@v4
with:
node-version: "24"
registry-url: "https://registry.npmjs.org"
- name: Copy root README into package
run: cp README.md packages/core/README.md
- name: Create Release Pull Request or Publish
id: changesets
uses: changesets/action@v1
with:
version: vp exec changeset version
publish: vp exec changeset publish
title: "chore: version packages"
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_CONFIG_PROVENANCE: "true"