ci: use buildspace typescript-service-release for telegram-ts#1
ci: use buildspace typescript-service-release for telegram-ts#1Yan Xue (yanxue06) wants to merge 1 commit into
Conversation
Replace the bespoke spec-driven release workflow with a call to the shared photon-hq/buildspace/.github/workflows/typescript-service-release.yaml@main reusable workflow, matching how spectrum-ts and advanced-imessage-ts release. Publishing now uses the standard label-driven flow (OpenAI-generated version + notes, gated on a `release` PR label) with OIDC Trusted Publishing, instead of mirroring the Telegram Bot API version via scripts/compute-version.ts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThe release workflow is refactored to delegate npm publishing orchestration to a centralized reusable workflow. Inline job steps for checkout, build, test, versioning, and npm publish with provenance are removed; the workflow now invokes a shared release template, passing configuration inputs and inheriting secrets. ChangesRelease workflow centralization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR migrates the telegram-ts release automation from a bespoke, spec-driven workflow to the shared photon-hq/buildspace reusable workflow, aligning the repo’s release process with other TypeScript services.
Changes:
- Replaced the in-repo release job steps with a call to
photon-hq/buildspace/.github/workflows/typescript-service-release.yaml. - Simplified the trigger to run on pushes to
mainand updated workflow permissions for OIDC-based publishing.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| on: | ||
| push: | ||
| branches: [main] | ||
| paths: | ||
| - "specs/telegram-bot-api.openapi.json" | ||
| workflow_dispatch: | ||
|
|
| permissions: | ||
| contents: write # create git tag + GitHub Release | ||
| id-token: write # OIDC token exchange for npm Trusted Publishing | ||
|
|
||
| concurrency: | ||
| group: release | ||
| cancel-in-progress: false | ||
| contents: write | ||
| pull-requests: read | ||
| id-token: write | ||
|
|
| gh release create "$TAG" \ | ||
| --title "$TAG" \ | ||
| --notes "Telegram Bot API ${{ steps.version.outputs.telegram_version }} — published \`@photon-ai/telegram-ts@${{ steps.version.outputs.version }}\`." | ||
| uses: photon-hq/buildspace/.github/workflows/typescript-service-release.yaml@main |
Enrolls
telegram-tsinto buildspace releases by replacing the bespoke spec-driven release workflow with a call to the shared reusable workflow, matching how spectrum-ts and advanced-imessage-ts release.Behavior changes
release-labeled PR merge tomain(OpenAI-generated version + notes), with OIDC Trusted Publishing — same flow as the other TS packages.10.0.0↔ Bot API 10.0); the workflow generates its own semver.scripts/compute-version.tsis now unused by the release path.specs/telegram-bot-api.openapi.jsonchanges.Follow-up
update-telegram-openapi.yamlopens spec-update PRs labeledtelegram-spec-update. Under the new flow those won't publish unless they also carry thereleaselabel — worth a follow-up to relabel/add it if hands-off spec publishing should continue.Requires
OPENAI_API_KEY(inherited viasecrets: inherit; spectrum-ts already relies on it).@photon-ai/telegram-ts(this repo + workflow).🤖 Generated with Claude Code
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.Summary by CodeRabbit
Release Notes
This release contains no changes visible to end-users. Updates were made to internal development infrastructure and automation processes to improve deployment efficiency.