Skip to content

chore(deps,docker,web-dev): Bump node from 20-slim to 26-slim in /web-dev#4

Closed
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/docker/web-dev/node-26-slim
Closed

chore(deps,docker,web-dev): Bump node from 20-slim to 26-slim in /web-dev#4
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/docker/web-dev/node-26-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor

Bumps node from 20-slim to 26-slim.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

iret77 and others added 4 commits May 9, 2026 19:49
Omadia — an Agentic OS for plugin-based AI agents.

This is the first public release of Omadia, extracted from byte5's
internal development tree. The full pre-public commit history (~250
commits across April–May 2026, including the brand-rename sweep, the
byte5-customer plugins moved out of the public scope, and the
deployment infrastructure that lives at byte5) is preserved privately
at byte5ai/omadia-pre-public-history for byte5 maintainers; this
repo starts fresh so that the public surface stays focused on the
kernel + reference plugins.

What this release ships:

Kernel SDK (under @omadia/* on npm):
  @omadia/plugin-api          — public plugin contract surface
  @omadia/channel-sdk         — channel-agnostic outgoing message types
  @omadia/orchestrator        — turn loop, tool dispatch, streaming
  @omadia/orchestrator-extras — context retriever, fact extractor,
                                topic detector, graph backfill
  @omadia/knowledge-graph-{inmemory,neon} — KG capability providers
  @omadia/embeddings          — embedding capability
  @omadia/memory              — memory store
  @omadia/diagrams            — diagram rendering pipeline
  @omadia/verifier            — answer-verification capability

Plugin-store-installable plugins:
  @omadia/plugin-quality-guard          — manifest + spec quality gating
  @omadia/plugin-privacy-guard          — Privacy-Proxy with detector pipeline
  @omadia/plugin-privacy-detector-{ollama,presidio} — NER detectors
  @omadia/plugin-web-search             — web-search tool

Reference agents:
  @omadia/agent-reference-maximum       — exercises every plugin-API
                                          capability, fork as starting point
  @omadia/agent-seo-analyst             — focused tool-only example

Built-in plugins (in middleware/src/plugins/):
  builder                               — UI-driven plugin authoring loop
                                          (codegen, slot typecheck, eslint
                                          auto-fix, runtime smoke harness)
  routines                              — user-authored cron-triggered
                                          agent runs with run-history viewer

Auth: multi-provider login (local password + Microsoft Entra ID OIDC),
admin UI for provider toggle and user management, audit log.

OSS-stack: Dockerfile (repo root + web-dev) for production build, MIT-
licensed.

Not in this release (lives in operator's deployment repo):
  - Production deployment infra (Fly.io, kroki, ollama, presidio-sidecar
    deployment configs)
  - byte5-customer plugin packages (channel-teams, channel-telegram,
    integration-{microsoft365,odoo,confluence}, agent-odoo-{accounting,
    hr}, agent-confluence) — installable via the plugin-store ZIP
    upload flow
  - Internal development docs (handoffs, briefings, plans)

The companion documentation is under README.md. For contribution
guidance see CONTRIBUTING.md, and for security disclosures see
SECURITY.md.
Bumps node from 20-slim to 26-slim.

---
updated-dependencies:
- dependency-name: node
  dependency-version: 26-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: deps, docker, web-dev. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot @github

dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/docker/web-dev/node-26-slim branch May 11, 2026 08:24
Weegy added a commit that referenced this pull request May 28, 2026
Plugins can now declare an optional Zod `output` schema on each tool.
The bridge validates the tool's return value against the schema; a
mismatch is recorded as a structured postcondition marker on the
RunTrace and surfaces as a synthetic `tool_postcondition` claim
(status='contradicted') in the verifier verdict.

That contradicted verdict flips the aggregate to `blocked` and feeds
into the existing `correctionPrompt` retry loop in `VerifierService`,
so no new retry pathway is introduced — the orchestrator simply re-runs
the turn with a German "Tool-Output nicht spec-konform" section in the
correction hint, instructing the model to re-call the tool with fixed
arguments or pick a different tool.

Backwards-compatible: tools without an `output` schema behave exactly
as before; `LocalSubAgentTool.handle` returns a `string | LocalSubAgentToolResult`
union so existing plugins keep returning strings unchanged.

Touches the cross-package run-trace shape: `RunToolCall.postcondition`
is mirrored in `@omadia/plugin-api` (KG-side) and `@omadia/channel-sdk`
(structural copy lifted in S+10-2).

Addresses #130 (Recommendation #4, May 2026 LLM-harness audit).

Tests: 14 new (verifierPipeline +2 — blocks-on-violation, backward-compat;
correctionPromptPostcondition +3 — section emitted, isolated from other
sections, undefined for non-blocked verdicts). Full middleware suite:
2629/2634 pass (3 preexisting privacyV4Bypass fails unrelated to #130).

Co-authored-by: Claude Opus 4.7 (1M context) <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.

2 participants