Skip to content

chore: bump owletto submodule to ship guardrails UI#924

Merged
buremba merged 1 commit into
mainfrom
chore/bump-owletto-guardrails
May 19, 2026
Merged

chore: bump owletto submodule to ship guardrails UI#924
buremba merged 1 commit into
mainfrom
chore/bump-owletto-guardrails

Conversation

@buremba
Copy link
Copy Markdown
Member

@buremba buremba commented May 19, 2026

Summary

Bumps packages/owletto from f611c1dd4f7c7571 (owletto's current main), bringing in the per-agent guardrail toggle + recent trips view (owletto PR #194).

Companion to:

With this bump the guardrails UI ships end-to-end.

Test plan

  • make build-packages clean
  • bun run typecheck clean
  • Submodule SHA 4f7c7571 is reachable on origin/main of lobu-ai/owletto

Summary by CodeRabbit

  • Chores
    • Updated internal submodule dependency to the latest version.

Review Change Stack

Bumps packages/owletto from 970eb500 → 4f7c7571 (origin/main), bringing
in the per-agent guardrail toggle + recent trips view (owletto PR #194).

Companion to the guardrails runtime work merged in #919 (call sites +
secret-scan + forbidden-tools built-ins) and #915 (schema + judge engine
+ pii-scan). With this bump the guardrails UI ships end-to-end.
@buremba buremba merged commit 464d228 into main May 19, 2026
17 checks passed
@buremba buremba deleted the chore/bump-owletto-guardrails branch May 19, 2026 16:12
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 19, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 04f058eb-a80c-47fa-bc2e-e6c91604e0ec

📥 Commits

Reviewing files that changed from the base of the PR and between a66c00d and 3ac6176.

📒 Files selected for processing (1)
  • packages/owletto

📝 Walkthrough

Walkthrough

The packages/owletto submodule reference was updated from one pinned commit to another, changing the version of the included subproject.

Changes

Owletto Submodule Update

Layer / File(s) Summary
Owletto submodule pointer update
packages/owletto
The packages/owletto submodule commit hash was updated to point to a new pinned commit.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

  • lobu-ai/lobu#886: Submodule pointer bump for packages/owletto to a different pinned commit.
  • lobu-ai/lobu#825: Submodule pointer update for packages/owletto changing the pinned commit hash.
  • lobu-ai/lobu#866: Submodule commit pointer update for packages/owletto to a new pinned version.

Poem

🐰 A tiny hash, a single bound,
The submodule pointer shifts around,
One commit out, another in—
Let fresh code flow and bugs rescind! ✨

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-owletto-guardrails

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov-commenter
Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

buremba added a commit that referenced this pull request May 19, 2026
…lock image builds (#927)

PR #911 added `examples/personal-finance` to root `package.json`'s
`workspaces` field but didn't update the Dockerfiles, which only COPY
`packages/*/package.json` for the install layer. `bun install` inside
the Docker build then errored:

    error: Workspace not found "examples/personal-finance"
        at /app/package.json:8:5

Every image build on `main` since #911 merged (13:25 UTC today) has
been red: #911#913 (+revert) → #914#915#919#923#924#912#925 — all sitting on `main` un-deployable, including the
`principal_kind` migration from #923 and my own loading-skeletons
shipping artifacts.

Two ways to fix it:

1. **Add stubs to all three Dockerfiles** for the example. Treats the
   symptom; couples prod build pipeline to whatever's under `examples/`,
   wrong direction.
2. **Take the example out of root workspaces.** Examples are
   documentation/demos for users to clone + run; they don't belong in
   the prod build graph. Cleaner separation.

Going with (2). Side effects:

- Example's dependency on `@lobu/promptfoo-provider` switched from
  `workspace:*` (workspace-protocol-only) to
  `file:../../packages/promptfoo-provider`. Resolves locally without
  requiring the example to be in a workspace; consumers run
  `cd examples/personal-finance && bun install` standalone (after
  building the provider once: `cd packages/promptfoo-provider && bun
  run build`).
- `bun.lock` regenerated. Most of the diff is bun's "linked
  workspaces" table shrinking — no upstream version churn.

Verified: simulated Docker build context (root files + stubbed
packages/* manifests + provider stub, no examples/) runs `bun install`
cleanly. No "Workspace not found" error.
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