docs(ci): add deprecation notice w/ Aug 8, 2026 shutoff date#544
Merged
Conversation
Surface the Shorebird CI deprecation on every CI doc page now that the customer-facing banner (shorebirdtech/_shorebird#2208) has shipped. Anyone landing on any CI page should see the shutoff date and a link to the migration guide before reading further. On the overview page, replaces the existing beta note since the product is past the beta-vs-deprecated question.
eseidel
approved these changes
May 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Shorebird CI is being shut down on August 8, 2026 and new sign-ups are already closed in the dashboard. Adding the same notice to every public CI doc page so anyone evaluating the product reads the deprecation before they read the setup steps.
Replaces the "currently in beta" note on the overview page since the product is past that question.
Testing
npm run buildclean, 59 pages built, all internal links valid