Skip to content

chore(installer): main → @armoriq/sdk (prod) + platform.armoriq.ai#16

Closed
Harihara04sudhan wants to merge 1 commit into
mainfrom
chore/installer-prod-sdk-and-dashboard-url
Closed

chore(installer): main → @armoriq/sdk (prod) + platform.armoriq.ai#16
Harihara04sudhan wants to merge 1 commit into
mainfrom
chore/installer-prod-sdk-and-dashboard-url

Conversation

@Harihara04sudhan

Copy link
Copy Markdown
Contributor

Summary

Flips install_armorcodex.sh on main to the production SDK channel + production frontend URL, establishing the dev/main split for the installer mirroring the config.mjs split already on the dev branch.

Branch SDK npm package Dashboard URL
dev @armoriq/sdk-dev https://dev.armoriq.ai
main (this PR) @armoriq/sdk https://platform.armoriq.ai

Why

Production users curl armoriq.ai/install_armorcodex.sh which serves whatever's on main (via the armoriq-landing mirror). Before this change, main had the -dev SDK channel + the dev dashboard URL hardcoded — meaning new prod installs would have:

  1. Pulled the dev npm package (could lag prod by features / be unstable)
  2. Pointed end users at dev.armoriq.ai for "dashboard visibility" — wrong audience

This brings the installer in line with the prod/staging boundary we already have for backendEndpoint in config.mjs.

Diff scope

Pure constant replacement — 8 lines changed in one file. No logic changes. No new dependencies.

Promotion semantics

When promoting a feature from dev → main (e.g., the latency-port PR #15), resolve any conflict on these two values in favor of main so prod users stay on prod.

Test plan

  • Run bash install_armorcodex.sh from a clean checkout of main after merge → confirm:
    • info "installing ArmorIQ CLI (@armoriq/sdk)" (not -dev)
    • "Unlocks: ... dashboard visibility for all intent plans at https://platform.armoriq.ai" in the connect-prompt section
  • After landing in main, the armoriq-landing mirror copy should be re-synced (separate small PR on armoriq-landing/public/install_armorcodex.sh)

🤖 Generated with Claude Code

Establishes the dev/main split for install_armorcodex.sh mirroring the
config.mjs split already in place:

  dev branch  → @armoriq/sdk-dev + https://dev.armoriq.ai
  main branch → @armoriq/sdk     + https://platform.armoriq.ai  (this PR)

`dev` stays at the dev/staging refs for pre-release verification.
When promoting a feature from dev → main, resolve the conflict in
favor of main so prod users never get pointed at dev resources.
Copilot AI review requested due to automatic review settings May 20, 2026 13:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the top-level install_armorcodex.sh installer on main to target production defaults (prod SDK package + prod dashboard URL) so new installs from the mirrored armoriq.ai/install_armorcodex.sh endpoint no longer pull dev-channel artifacts.

Changes:

  • Switches DASHBOARD_URL from https://dev.armoriq.ai to https://platform.armoriq.ai.
  • Switches installer references from @armoriq/sdk-dev to @armoriq/sdk for global install and npx login fallback.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Harihara04sudhan

Copy link
Copy Markdown
Contributor Author

Superseded by #12 which contains everything this PR does (DASHBOARD_URL → platform.armoriq.ai, @armoriq/sdk-dev → @armoriq/sdk) plus the idempotent update mode (--force-install / --update flags, detect_mode, run_update_path) and the updated docs URL (docs.armoriq.ai/armorcodex). Closing in favor of #12.

@Harihara04sudhan Harihara04sudhan deleted the chore/installer-prod-sdk-and-dashboard-url branch May 20, 2026 13:14
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.

2 participants