Repository navigation
ci: Run the compatibility matrix against merged SDKs' main branches - #8
Merged
Merged
Conversation
The spec PRs for the nine SDKs merged and their feat/sdk-spec branches were deleted, so the matrix failed checking them out. js-client keeps feat/sdk-spec until Flagsmith/flagsmith-js-client#430 merges.
khvn26
approved these changes
Oct 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.
The spec PRs for python, nodejs, java, dotnet, go, ruby, php, rust and elixir have merged, and their
feat/sdk-specbranches were deleted. The compatibility matrix still checked those branches out, so every job failed at checkout (for example on #5).This points those nine SDKs at
main, which is each repo's default branch. js-client keepsfeat/sdk-specuntil Flagsmith/flagsmith-js-client#430 merges.