Skip to content

feat: turn drive state reading and publishing on in production - #2335

Merged
vilenarios merged 1 commit into
devfrom
prod-drive-state-on
Oct 21, 2026
Merged

vilenarios merged 1 commit into
devfrom
prod-drive-state-on

Conversation

@vilenarios

Copy link
Copy Markdown
Collaborator

Turns Drive State on in production for this release, as staging has run it since 2026-10-16.

Change

  • assets/config/prod.json: enableSyncFromDriveState and enableDriveStatePublishing set to true, the same as staging.
  • configVersion goes from 3 to 4. Without the bump, anyone who has already run the app keeps their stored config, with both switches off (ConfigFetcher replaces the stored config only when the asset's configVersion is higher).
  • drive_state_publishing_rail_test.dart now expects staging and prod on, and dev off.

What users get

  • Reading: a sync reads a drive's newest snapshot before replaying its history. Reading costs one discovery query per drive, and any failure falls back to the normal sync.
  • Publishing: Create snapshot publishes the new format. Snapshots made by CLI 5.0.0 and core-js are readable here too.

Side effect of the configVersion bump

Replacing the stored config resets every setting a user changed in the app back to the asset defaults:

  • the gateway chosen in Settings → Switch Gateway (arweaveGatewayUrl);
  • the AR.IO gateway detected the first time someone opened the app from a gateway (arweaveGatewayForDataRequest), because detection runs only when there is no stored config at all;
  • the auto sync, thumbnail and snapshot-sync toggles.

The bump in #2200 (August 27) had the same effect. A follow-up could carry a user's own choices across a version bump.

Checks

  • test/drive_state/drive_state_publishing_rail_test.dart and test/services/config: 46 pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y4dehHVpH2fFgzitCz1yJ6

- prod.json: enableSyncFromDriveState and enableDriveStatePublishing on, as
  staging has run them since 2026-10-16
- configVersion 3 -> 4, so users who already ran the app take the new config;
  without the bump their stored config keeps both off
- the flag rail test now expects staging and prod on, dev off

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y4dehHVpH2fFgzitCz1yJ6
@coderabbitai

coderabbitai Bot commented Oct 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 6 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository: ardriveapp/ardrive-web/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: e823ba2c-ec3b-41a4-97e9-d8d24b6a1f6f
📥 Commits

Reviewing files that changed from the base of the PR and between ec2eae6 and a6de179.

📒 Files selected for processing: 2
  • assets/config/prod.json
  • test/drive_state/drive_state_publishing_rail_test.dart
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

Visit the preview URL for this PR (updated for commit a6de179):

https://ardrive-web--pr2335-prod-drive-state-on-874shhf1.web.app

(expires Wed, 28 Oct 2026 01:41:16 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: a224ebaee2f0939e7665e7630e7d3d6cd7d0f8b0

@vilenarios
vilenarios merged commit 7ad285e into dev Oct 21, 2026
7 checks passed
@vilenarios
vilenarios deleted the prod-drive-state-on branch October 21, 2026 01:42
@vilenarios vilenarios mentioned this pull request Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant