Skip to content

fix(ci): build the wasm image directly instead of via the r-wasm reusable workflow - #319

Merged
schloerke merged 1 commit into
mainfrom
schloerke/rwasm-fix
Sep 13, 2026
Merged

schloerke merged 1 commit into
mainfrom
schloerke/rwasm-fix

Conversation

@schloerke

Copy link
Copy Markdown
Collaborator

Follow-up to #318. The reusable workflow failed on r/v0.1.0: its rwasm::add_pkg() call leaves remotes = NA, which resolves rwasm's built-in list of webR package forks (r-wasm/shiny@webr and friends) from GitHub with no PAT — docker run does not forward GITHUB_TOKEN into the container. The container's older pkgdepends reports the failure as an opaque res_one_row_df(): nrow(out) must equal 1 (r-lib/pkgdepends#462 masks the real error).

We build only shinyreact (dependencies = FALSE, same as the reusable workflow), so the fork preferences are irrelevant and remotes = NULL skips that resolution entirely. Dependencies come from repo.r-wasm.org at runtime.

Verified on a scratch branch: the build produces library.data.gz (113 KB) + library.js.metadata, both now attached to https://github.com/posit-dev/shinyreact/releases/tag/r/v0.1.0.

…able workflow

release-file-system-image.yml leaves `remotes = NA` in `rwasm::add_pkg()`,
which resolves rwasm's built-in list of webR package forks from GitHub with no
PAT. That resolution fails here, surfacing as an opaque
`res_one_row_df(): nrow(out) must equal 1` from the container's older
pkgdepends. We build only shinyreact, so `remotes = NULL` skips it.

Refs #268
@schloerke
schloerke merged commit 0ff27a2 into main Sep 13, 2026
2 checks passed
@schloerke
schloerke deleted the schloerke/rwasm-fix branch September 13, 2026 20:29
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