Skip to content

build: bump cli v0.15.5 to fix missing custom functions in JS Rust build#110

Merged
peterpeterparker merged 2 commits into
mainfrom
feat/cli
Jun 5, 2026
Merged

build: bump cli v0.15.5 to fix missing custom functions in JS Rust build#110
peterpeterparker merged 2 commits into
mainfrom
feat/cli

Conversation

@peterpeterparker

Copy link
Copy Markdown
Contributor

Relates to junobuild/cli#515

@peterpeterparker peterpeterparker merged commit bc0eed8 into main Jun 5, 2026
6 checks passed
@peterpeterparker peterpeterparker deleted the feat/cli branch June 5, 2026 17:39
AntonioVentilii added a commit to AntonioVentilii/vici-app that referenced this pull request Jun 5, 2026
# Motivation

The CI satellite build was shipping with no custom query methods
(`IC0536 — Canister has no query method 'app_get_profile'`), breaking
production sign-in. Root cause was a juno CLI bug — the generated Rust
custom-functions module was not included in the `wasm32-wasip1`
satellite build. Fixed upstream in
[junobuild/cli#515](junobuild/cli#515), released
in **`@junobuild/cli@0.15.5`**.

# Changes

Bump the two **direct** CLI pins from `0.15.4` → `0.15.5`: `checks.yml`
(`satellite-schema`) and `e2e.yml`.

The action-based workflows need no change — `upgrade.yml`/`publish.yml`
use `junobuild/juno-action@full`, which now resolves to image `0.7.4`
bundling cli `0.15.5`
([junobuild/juno-action#110](junobuild/juno-action#110)),
so they already pick up the fix.

# Tests

The `e2e` job on this PR is the field test: with `0.15.5` the satellite
build now embeds the custom functions, so the signed-in flows (`auth`,
`homepage`, signed-in `navigation`) that were failing with
`getProfile()` errors should pass. Note: a separate, pre-existing `[404]
GET /social` routing failure and the 45-min e2e timeout are tracked
elsewhere (`fix/e2e-bounded-networkidle-and-timeout`) and are out of
scope here. `satellite-schema` should stay green (and now actually
regenerates against the fixed build).

Follow-up (not in this PR): `checks.yml`'s inline comment above the
install still references the old (incorrect) "bindgen → `service : {}`"
rationale and could be trimmed; left untouched here to keep the diff to
the version bump.
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