Skip to content

Canvas App: pin the vendored build; take canvas-app c425198 - #5

Open
collinrijock wants to merge 2 commits into
mainfrom
canvas/pin-canvas-app
Open

collinrijock wants to merge 2 commits into
mainfrom
canvas/pin-canvas-app

Conversation

@collinrijock

@collinrijock collinrijock commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Pins the vendored Canvas App (/canvas/) to a canvas-app commit and takes canvas-app main.

  • Pin. crates/copper-cloud/assets/CANVAS_APP_REF names the canvas-app commit whose dist/web/index.html is vendored as crates/copper-cloud/assets/canvas-app.html. packaging/sync-canvas-app.sh now works from it, like Copper's Canvas/sync.sh: no argument re-fetches the pinned build; REF pins a new commit and fetches it; --check compares the vendored file with the pinned build; --from FILE vendors a local build. The first commit pins 62228f5, which is what 0.11.1 ships (its file is byte-identical), so it changes no bytes.
  • Refresh to canvas-app c425198 (main). This brings in Continue with Google, link landings (#/join/…, #/c/… signed out), ?focus=, invites and the account menu (compare).

How it behaves when copper-cloud serves it (not canvas-cloud)

I checked this against a local copper-cloud built from this branch.

  • The page's GET /v1/info goes out without the gate header. It gets 401 {"error":"instance_key"}, so the app treats the origin as a plain static server. There are no SSO buttons and nothing calls /v1/auth/oidc/…, and the sign-in form keeps its Server / link code field, as in 0.11.1.
  • A signed-out share link (/canvas/#/join/<token>) now opens a "You've been invited to a canvas" card with that form, where it used to show a toast. The console shows no errors.
  • Once signed in with a link code, GET /v1/invites goes through the canvas link's existing /v1/invites proxy. If that fails, the app only hides the invites list.
  • On *.exowatt.com hosts, such as dev1, the app shows the Exowatt brand on its own screens (not on the board).

Tests

  • cargo test -p copper-cloud --locked --test canvas_app passes.
  • packaging/sync-canvas-app.sh --check reports canvas-app.html matches canvas-app c425198d038b….

The hourly sync workflow is stacked on top of this PR (next PR). Not merging; releases and dev1 deploys are Felipe's.

🤖 Generated with Claude Code

collinrijock and others added 2 commits October 21, 2026 00:03
crates/copper-cloud/assets/CANVAS_APP_REF names the canvas-app commit whose
dist/web/index.html is vendored as canvas-app.html (62228f5, what 0.11.1 ships).
packaging/sync-canvas-app.sh now works from the pin, as Copper's Canvas/sync.sh does:
no argument re-fetches the pinned build, REF pins a new commit and fetches it,
--check compares the vendored file with the pinned build, --from vendors a local one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ngs, invites, account menu)

Vendors canvas-app main's web build. Served by copper-cloud (not canvas-cloud) the new
sign-in paths stay out of the way: the page's GET /v1/info goes without the gate header,
gets 401 instance_key, and the app treats the origin as a plain static server, so there
are no single sign-on buttons and the sign-in form keeps its server / link-code field.
Signed in with a link code, invites list through the canvas link's /v1/invites proxy.

copper-browser/canvas-app@62228f5...c425198

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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