Skip to content

fix(ci): initialize owletto-web submodule in landing deploy#229

Merged
buremba merged 1 commit into
mainfrom
fix/deploy-landing-submodule
Apr 20, 2026
Merged

fix(ci): initialize owletto-web submodule in landing deploy#229
buremba merged 1 commit into
mainfrom
fix/deploy-landing-submodule

Conversation

@buremba
Copy link
Copy Markdown
Member

@buremba buremba commented Apr 20, 2026

Summary

  • Add setup-submodule action step to deploy-landing-cloudflare.yml (mirrors ci.yml pattern)
  • Conditionally skip --frozen-lockfile when the submodule is stubbed (no deploy key), since a stub package.json diverges from bun.lock

Context

The landing deploy workflow has been failing since the 3.6.0 release because packages/owletto-web (a git submodule) was never initialized. bun install --frozen-lockfile sees lockfile drift — the lockfile knows the submodule's real deps, but CI sees an empty directory, so dependency resolution computes a different hash.

Other workflows (ci.yml, pr-validation.yml) already use ./.github/actions/setup-submodule; this PR brings the landing deploy in line.

Test plan

@buremba buremba merged commit 0dee7bc into main Apr 20, 2026
8 of 9 checks passed
@buremba buremba deleted the fix/deploy-landing-submodule branch April 21, 2026 21:41
buremba added a commit that referenced this pull request May 26, 2026
Picks up: refactor(web): filled content cards rely on fill, not a border (#229)

Before: 79932d7
After:  d940389
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