Skip to content

Re-enable the TypeScript SDK release workflow - #679

Merged
levindixon merged 1 commit into
mainfrom
levin.dixon/re-enable-ts-sdk
Sep 23, 2026
Merged

levindixon merged 1 commit into
mainfrom
levin.dixon/re-enable-ts-sdk

Conversation

@levindixon

Copy link
Copy Markdown
Contributor

Why?

The TypeScript SDK has not been regenerated from the spec since February, because the release workflow was disabled along with the rest of this repo's automation. Bringing it back is the first step toward shipping a node release again, and it can come back safely now that the Fern token is stored only in a branch-restricted environment.

How?

Restores the manual release workflow with pinned actions, read-only permissions, and a job bound to that environment, so the Fern token is never available to code outside the default branch. Drops the npm token from the workflow and the generator config, since the SDK repository now publishes to npm on its own and Fern only needs to open a pull request there.

Notes for reviewers

Fern's config loader fails on any ${VAR} that is not set in the environment, so removing the token from the workflow alone would break generation. The npm output block accepts a missing token, and in pull-request mode Fern never publishes itself, so the two removals go together. Dispatching this workflow from any branch other than main should fail at the environment gate before a single step runs; that is the intended behaviour.

Generated with Claude Code

Move ts-sdk.yml back into .github/workflows. The release job now runs
in the main environment, which is the only place FERN_TOKEN exists and
whose branch policy limits it to runs from main. Pin actions/checkout,
actions/setup-node and pnpm/action-setup to commits, declare read-only
permissions, stop persisting git credentials, serialise runs, and cap
the job at 30 minutes. The version input is validated as semver and
passed through an environment variable instead of being interpolated
into the shell.

Drop FERN_NPM_TOKEN from both the workflow and the ts-sdk generator
output. intercom-node publishes to npm through its own release
workflow, and Fern only opens a pull request there. Fern's config
loader fails on an undefined ${VAR}, so the two removals go together.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@levindixon
levindixon merged commit 4bc74e6 into main Sep 23, 2026
4 checks passed
@levindixon
levindixon deleted the levin.dixon/re-enable-ts-sdk branch September 23, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants