<?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 UpdatesDatabaseMigrationRegistry.swift</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>54bfa6bf - [expo-updates][ios] Make updates.manifest column non-nullable (#23167)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift#54bfa6bf</link>
        <description>[expo-updates][ios] Make updates.manifest column non-nullable (#23167)

            List of files:
            /expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift</description>
        <pubDate>Thu, 17 Aug 2023 23:31:26 +0000</pubDate>
        <dc:creator>Will Schurman &lt;wschurman@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>17709897 - [exupdates][ios] Run swiftlint --fix (#21664)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift#17709897</link>
        <description>[exupdates][ios] Run swiftlint --fix (#21664)# WhyTo appease the swiftlint gods.# Test PlanBuild.# 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 `expo prebuild` &amp; EAS Build (eg:updated a module plugin).

            List of files:
            /expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift</description>
        <pubDate>Fri, 10 Mar 2023 17:22:20 +0000</pubDate>
        <dc:creator>Will Schurman &lt;wschurman@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>5683b337 - [exupdates][ios] rename swift classes to be more swifty (#21620)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift#5683b337</link>
        <description>[exupdates][ios] rename swift classes to be more swifty (#21620)# WhyAs requested by @douglowder. These classes can be better-named and thenjust expose the `EXUpdates` prefix in objective-c type names.# HowRename. Going to land this very soon to avoid bad merge conflicts. I&apos;mexpected swiftlint will fail on this and will eat up all our API quotaas well.# Test PlanBuild and run expo go, run all tests.# 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 `expo prebuild` &amp; EAS Build (eg:updated a module plugin).

            List of files:
            /expo/packages/expo-updates/ios/EXUpdates/Database/Migrations/UpdatesDatabaseMigrationRegistry.swift</description>
        <pubDate>Wed, 08 Mar 2023 22:51:41 +0000</pubDate>
        <dc:creator>Will Schurman &lt;wschurman@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
