fix(web): URL-sync /tags topic-filter search box (#5712) (#5735) #1077
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-please | |
| # Conventional-commit-driven release automation for the @heyclaude/mcp package. On | |
| # every push to main, release-please maintains a "Release PR" that bumps the SemVer | |
| # and regenerates packages/mcp/CHANGELOG.md from the conventional commits. Merging | |
| # the Release PR tags the package (mcp-v<semver>) and creates the GitHub Release, | |
| # then dispatches publish-mcp-npm.yml (OIDC trusted publishing + provenance) via the | |
| # Dispatch step below. | |
| # | |
| # A tag-push trigger can't be used: GITHUB_TOKEN-created tags don't fire workflows, | |
| # and the publish gate (scripts/validate-mcp-release.sh) requires | |
| # GITHUB_REF=refs/heads/main. A bare manual dispatch of publish-mcp-npm.yml remains | |
| # the override path (it self-tags). Commits are already Conventional Commits, so the | |
| # changelog is generated, not hand-maintained. | |
| # | |
| # Authenticates via RELEASE_PLEASE_TOKEN (a fine-grained PAT), not the default | |
| # GITHUB_TOKEN -- see the "Run release-please" step below for why. | |
| on: | |
| push: | |
| branches: | |
| - main | |
| permissions: | |
| contents: write | |
| pull-requests: write | |
| actions: write # dispatch publish-mcp-npm after a release | |
| concurrency: | |
| group: release-please | |
| cancel-in-progress: false | |
| jobs: | |
| release-please: | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 15 | |
| steps: | |
| - name: Checkout | |
| uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd | |
| with: | |
| persist-credentials: false | |
| # Authenticates as a real account (via RELEASE_PLEASE_TOKEN, a fine-grained PAT) rather than the | |
| # default GITHUB_TOKEN. GitHub Apps like github-actions[bot] aren't tracked as repo collaborators, | |
| # so PRs/commits it authors were repeatedly re-flagged as needing manual workflow-run approval on | |
| # every push, even with the least-restrictive fork-PR-approval setting -- a real collaborator | |
| # identity doesn't hit that gate. | |
| - name: Run release-please | |
| id: release | |
| uses: googleapis/release-please-action@5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 # v4.4.1 | |
| with: | |
| config-file: release-please-config.json | |
| manifest-file: .release-please-manifest.json | |
| token: ${{ secrets.RELEASE_PLEASE_TOKEN }} | |
| # release-please creates the component tag (mcp-v<semver>) + GitHub Release. | |
| # Even with a real-account PAT, tag/release creation doesn't fire push/tag-based | |
| # workflows here, so workflow_dispatch is used explicitly to dispatch the OIDC | |
| # publish workflow, telling it release-please already created the tag/release. | |
| # Without this, merging a Release PR would never publish to npm. | |
| - name: Dispatch npm publish | |
| if: ${{ steps.release.outputs['packages/mcp--release_created'] == 'true' }} | |
| env: | |
| GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| run: gh workflow run publish-mcp-npm.yml --ref main -f released_by_release_please=true |