Skip to content

Force UI testnet publish without redeploying contracts - #161

Merged
AdamSpitz merged 1 commit into
devfrom
fix/force-ui-deploy
Sep 3, 2026
Merged

Force UI testnet publish without redeploying contracts#161
AdamSpitz merged 1 commit into
devfrom
fix/force-ui-deploy

Conversation

@AdamSpitz

Copy link
Copy Markdown
Owner

Why

PR #160 put the setup-env.sh skip on master. Deploy 33813940624 correctly skipped contracts, then also skipped UI because the merge only touched that script. Testnet bundles still have not been published with the current Base Sepolia addresses.

What

  • workflow_dispatch input force_ui (same shape as force_contracts) so we can publish UI without rotating contracts.
  • Treat scripts/setup-env.sh and scripts/deploy-testnet.sh as UI-related so a future env-setup-only merge actually runs ./scripts/deploy-testnet.sh.

After this reaches master, dispatch Deploy to Testnet with force_ui=true and force_contracts=false.

…t files.

#158 left addresses on master but UI failed on a missing env file. #160
landed the setup-env skip, then skipped UI because only that script
changed. Manual dispatch can now publish UI without rotating contracts.

@AdamSpitz AdamSpitz left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review receipt.

Workflow-only: force_ui dispatch mirrors force_contracts; path filter adds the two deploy scripts. Metadata-updated still blocks UI until addresses land. No findings.

Reviewed-with: grok
Reviewed-files: 1
Reviewed-commit: 9b3fb38

@AdamSpitz
AdamSpitz merged commit d379292 into dev Sep 3, 2026
8 checks passed
@AdamSpitz
AdamSpitz deleted the fix/force-ui-deploy branch September 4, 2026 00:19
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