You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -211,45 +211,71 @@ Set up a release workflow via [GitHub Actions](https://docs.github.com/en/action
211
211
</Step>
212
212
<Step title="Set up a new workflow">
213
213
214
-
In your repo, navigate to **Actions**. Select **New workflow**, then **Set up workflow yourself**. Set up a workflow dispatch that is similar to this:
214
+
In your repo, navigate to **Actions**. Select **New workflow**, then **Set up workflow yourself**. Set up a CI workflow that automatically publishes on tagged pushes:
To trigger a release, create and push a git tag to your repository. The workflow will automatically run and publish your package to npm.
253
279
254
280
Once your workflow completes, log back into npm and
255
281
navigate to **Packages** to see your new release.
@@ -264,21 +290,21 @@ Set up a release workflow via [GitHub Actions](https://docs.github.com/en/action
264
290
265
291
Add `token: ${NPM_TOKEN}` to `generators.yml` to tell Fern to use the `NPM_TOKEN` environment variable for authentication when publishing to the npm registry.
When you regenerate your release, Fern will automatically create a workflow in your repository called `.github/workflows/ci.yml` that will automatically publish your release to npm. For an example, see Vapi's [npm publishing GitHub Action](https://github.com/VapiAI/server-sdk-typescript/blob/main/.github/workflows/ci.yml)
0 commit comments