Skip to content

ci: remove the Buildkite CDN release pipeline - #1391

Merged
abueide merged 2 commits into
masterfrom
remove-buildkite-cdn-pipeline
Jul 21, 2026
Merged

ci: remove the Buildkite CDN release pipeline#1391
abueide merged 2 commits into
masterfrom
remove-buildkite-cdn-pipeline

Conversation

@abueide

@abueide abueide commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Reverses #1382. CDN release is moving to a GitHub Actions-based deploy instead of Twilio Buildkite.

  • Removes .buildkite/pipeline.yml
  • Removes publish.yml's "Trigger CDN release build" step (Buildkite API call + BUILDKITE_API_TOKEN)
  • Updates the dead Segment Buildkite CI badge in README.md to point at the GHA ci.yml workflow
  • Fixes a stale (Buildkite) reference in RELEASING.md left over from before the CI migration

No replacement GHA-based S3 deploy step is added here - that's separate follow-up work.

Test plan

  • Confirm publish.yml still runs end-to-end (npm publish path is unaffected by this change)

abueide added 2 commits July 21, 2026 11:08
Reverses #1382. CDN release is moving to a GitHub Actions-based
deploy instead - the Twilio Buildkite pipeline, its trigger step in
publish.yml, and the now-broken legacy CI badge are all removed.

No replacement deploy step is added here; that's separate follow-up
work.
Follow-up to the previous commit - removes publish.yml's Buildkite
API trigger step, updates the dead Segment Buildkite CI badge in
README.md to point at the GHA ci.yml workflow instead, and fixes a
stale "(Buildkite)" doc reference in RELEASING.md that predates this
migration.
@tvs-twilio-segment

Copy link
Copy Markdown

✅ TVS Validation Passed

View full report

Show details

All validation checks have successfully completed.

@changeset-bot

changeset-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0b04759

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.59%. Comparing base (99ac8ca) to head (820253f).
⚠️ Report is 1 commits behind head on master.

⚠️ Current head 820253f differs from pull request most recent head 0b04759

Please upload reports for the commit 0b04759 to get more accurate results.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1391   +/-   ##
=======================================
  Coverage   91.59%   91.59%           
=======================================
  Files         127      127           
  Lines        4142     4142           
  Branches     1033     1033           
=======================================
  Hits         3794     3794           
  Misses        348      348           
Flag Coverage Δ
browser 92.51% <ø> (ø)
core 90.07% <ø> (ø)
node 89.43% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@abueide
abueide enabled auto-merge (squash) July 21, 2026 16:11
@abueide
abueide merged commit 6cd4068 into master Jul 21, 2026
35 of 37 checks passed
@abueide
abueide deleted the remove-buildkite-cdn-pipeline branch July 21, 2026 16:12
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