Don't output a blank line before a tool call error #23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Release | |
| on: | |
| push: | |
| branches: | |
| - main | |
| concurrency: ${{ github.workflow }}-${{ github.ref }} | |
| # This workflow will run changesets depending on two different scenarios: | |
| # | |
| # 1. If we are landing a specific commit into main (Author PR), then | |
| # changesets will check if there are changes verifying the Markdown files | |
| # generated automatically: | |
| # | |
| # a) There are new versions and there's NO Release PR, then the changesets | |
| # action will create a new Release PR. | |
| # | |
| # b) There's a Release PR, then the changesets action will update the | |
| # existing Release PR with the new commit. | |
| # | |
| # NOTE: (in both cases, changesets will modify the new version in | |
| # package.json for each package, and will remove the MD files as part of the | |
| # Release PR). | |
| # | |
| # 2. If we are landing the Release PR into main, then the changesets action | |
| # will publish the changes to npm. | |
| # | |
| # For more info about this workflow, see: | |
| # https://github.com/changesets/action#usage | |
| jobs: | |
| release: | |
| name: Release | |
| runs-on: ${{ matrix.os }} | |
| strategy: | |
| matrix: | |
| os: [ ubuntu-latest ] | |
| node-version: [ 24.x ] | |
| permissions: | |
| id-token: write # For trusted publishing to npm (includes provenance) | |
| contents: write # For GitHub pages and creating release PRs | |
| steps: | |
| - uses: actions/checkout@v4 | |
| with: | |
| fetch-depth: 0 | |
| - name: Setup Node | |
| uses: actions/setup-node@v6 | |
| with: | |
| node-version: ${{ matrix.node-version }} | |
| - name: Install pnpm | |
| uses: pnpm/action-setup@v4 | |
| with: | |
| run_install: false | |
| - name: Install node_modules | |
| run: | | |
| pnpm install --frozen-lockfile | |
| # NPM trusted publishing requires npm CLI v11.5.1+. Node.js 22 ships with | |
| # npm 10.x, so we need to upgrade. Note that pnpm uses npm under the hood | |
| # for publishes. | |
| - name: Upgrade npm for OIDC support | |
| run: | | |
| npm install -g npm@11.11.0 | |
| echo "✅ npm upgraded to $(npm --version)" | |
| - name: Create Release Pull Request or Publish to npm | |
| id: changesets | |
| uses: changesets/action@c48e67d110a68bc90ccf1098e9646092baacaa87 # v1.6.0 | |
| with: | |
| publish: pnpm publish:ci | |
| env: | |
| # We use a Personal Access Token here rather than the GITHUB_TOKEN | |
| # so that it will trigger our other actions. The token has to be on | |
| # the account of someone with appropriate access levels and given the | |
| # repo scope. | |
| GITHUB_TOKEN: ${{ secrets.KHAN_ACTIONS_BOT_TOKEN }} | |
| # NPM_CONFIG_PROVENANCE is for trusted publishing. We set this so | |
| # that (p)npm publish will include the provenance information in the | |
| # package.json file and surface it in the npm registry. See: | |
| # - https://docs.npmjs.com/generating-provenance-statements | |
| # - https://khanacademy.atlassian.net/wiki/spaces/FRONTEND/blog/4432363720/npm+Trusted+Publishing | |
| NPM_CONFIG_PROVENANCE: true |