<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in BranchesForProjectQuery.query.graphql</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4bf298e0 - [expo-go] change project/branch screens to query updates by sdkVersion (#22511)</title>
        <link>http://172.16.0.5:8080/history/expo/home/graphql/queries/BranchesForProjectQuery.query.graphql#4bf298e0</link>
        <description>[expo-go] change project/branch screens to query updates by sdkVersion (#22511)# WhyWe want to deprecate `sdkVersion` runtime, but still want to let usersdevelop in Expo Go if they are using a supported SDK version.In the Expo Go project view, we filter all the updates by supported`runtimeVersion` (ie) `expoSdk:48.0.0`. This means anyone on a runtimepolicy like `appVersion` wont have any of their updates show up eventhough they are on a supported sdk.&lt;imgsrc=&quot;https://github.com/expo/universe/assets/6380927/e96f1db2-201e-4e14-98d2-86d15a3102c2&quot;width=&quot;200&quot; height=&quot;400&quot; /&gt;# HowQuery updates  by `sdkVersion` instead of `runtimeVersion` in Graphql.# Test Plan- [ ] I loaded the JS into the unversioned Expo Go and it works&lt;img width=&quot;310&quot; alt=&quot;Screenshot 2023-05-16 at 10 30 41 PM&quot;src=&quot;https://github.com/expo/expo/assets/6380927/ebf9d783-c970-422b-bfca-3a370febe037&quot;&gt;# Checklist&lt;!--Please check the appropriate items below if they apply to your diff.This is required for changes to Expo modules.--&gt;- [ ] Documentation is up to date to reflect these changes (eg:https://docs.expo.dev and README.md).- [ ] Conforms with the [Documentation Writing StyleGuide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)- [ ] This diff will work correctly for `npx expo prebuild` &amp; EAS Build(eg: updated a module plugin).

            List of files:
            /expo/home/graphql/queries/BranchesForProjectQuery.query.graphql</description>
        <pubDate>Wed, 17 May 2023 18:57:33 +0000</pubDate>
        <dc:creator>Quinlan Jung &lt;quin@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>be37628c - [home] implement redesigned project details and branch-related screens (#16699)</title>
        <link>http://172.16.0.5:8080/history/expo/home/graphql/queries/BranchesForProjectQuery.query.graphql#be37628c</link>
        <description>[home] implement redesigned project details and branch-related screens (#16699)* scaffold using existing project page* refactor warning box and classic updates button* redesign empty section* pull classic updates section into its own file* move eas update section into its own file* redesign updates section* add constants section* [home] implement branch list screen (#16708)* [home] implement branch list screen* [home] implement branch details page (#16710)* [home] implement branch details page* use exp protocol to open updates in Expo Go* remove kitchen sink* update recently updated section to ignore invalid EAS Updates* use flatlist for branch details update list

            List of files:
            /expo/home/graphql/queries/BranchesForProjectQuery.query.graphql</description>
        <pubDate>Fri, 25 Mar 2022 15:43:31 +0000</pubDate>
        <dc:creator>Juwan Wheatley &lt;datwheat@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
