v2.3.0

Dashboard Improvements

• Display rollback status in the updates table
• Add an update details view showing the Expo config and all relevant information
• Use default API_URL=http://localhost:3000 for development environment
• Remove dist folder from Git
• Remove duplicated dashboard folder caused by a bad merge in a previous commit

EOAS

• Channel no longer required for the publish command:
  Previously, the channel field was required to set the RELEASE_CHANNEL environment variable used for private config generation. Now, users are expected to provide your environment to eoas publish command. (ex: RELEASE_CHANNEL=X npx eoas publish --branch X).
  For backward compatibility, if the deprecated channel field is still submitted, RELEASE_CHANNEL will be automatically populated.
• New rollback command:
  Allows publishing a rollback to a specific branch/runtimeVersion.
  ⚠️ Not compatible with disableAntiBrickingMeasure, as expo-updates will ignore embedded updates in that case.
• New republish command:
  Enables republishing a previous update to a specific branch/runtimeVersion.

Global Server Changes

• Migration system:
  Migrations can now be configured in the migrations folder.
  They will automatically run on startup, using a lock system to avoid duplicate runs.
• Persisted UUIDs:
  UUIDs are now persisted in update-metadata.json during upload.
  This ensures that future changes to UUID generation won’t break previous updates.
  A migration has been added to retroactively generate consistent UUIDs for existing updates.
• GetFile now returns a pointer
  The GetFile method on buckets now returns a pointer to BucketFile, making it easier to handle missing file scenarios instead of immediately throwing an error.
• Server versioning & cache invalidation:
  Versioning has been added to the server along with cache keys, ensuring cache is properly reset on each deployment.
  The version is injected at build time via CI.
  -UUID collision fix
  Previously, republishing the same code or reusing update identifiers could lead to UUID collisions.
  UUIDs are now generated based on the update timestamp and a fingerprint is added in the metadata to guarantee uniqueness.
  -Improved API sub-router
  The API sub-router now supports authentication using an Expo token or session, allowing direct usage from the EOAS CLI.

Cache

• Add global cache prefix to prevent collisions

v2.2.8

Changes

• Docker image: ghcr.io/axelmarciano/expo-open-ota:v2.2.8
• Helm chart version updated

v2.2.7

Changes

• Docker image: ghcr.io/axelmarciano/expo-open-ota:v2.2.7
• Helm chart version updated

v2.2.6

What's Changed

• Replace #6 – Add retries to make publish resilient against network instability and outputDir flag by @axelmarciano in #7

Full Changelog: v2.2.5...v2.2.6

v2.2.5

Changes

• Docker image: ghcr.io/axelmarciano/expo-open-ota:v2.2.5
• Helm chart version updated

v2.2.4

Changes

• Docker image: ghcr.io/axelmarciano/expo-open-ota:v2.2.4
• Helm chart version updated

v2.2.3

Changes

• Docker image: ghcr.io/axelmarciano/expo-open-ota:v2.2.3
• Helm chart version updated

v2.2.1

Full Changelog: v2.2.0...v2.2.1

v2.2.0

What's Changed

• feat: add dashboard & prometheus metrics by @axelmarciano in #4

Full Changelog: v2.1.0...v2.2.0

v2.1.0

What's Changed

• feat: support redis for cache by @axelmarciano in #3

Full Changelog: v2.0.0...v2.1.0