Skip to content

chore(OMN-16997): bump omnibase-infra to 0.38.14 - #464

Merged
jonahgabriel merged 3 commits into
devfrom
automation/bump-omnibase-infra-0.38.14
Aug 31, 2026
Merged

jonahgabriel merged 3 commits into
devfrom
automation/bump-omnibase-infra-0.38.14

Conversation

@onexbot-occ-writer

@onexbot-occ-writer onexbot-occ-writer Bot commented Aug 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Automated dependency bump triggered by a new release of omnibase_infra (v0.38.14).

  • Updates uv.lock via uv lock --upgrade-package omnibase_infra
  • Updates pyproject.toml exact pins (==X.Y.Z) to match resolved version

Triggered by

Release workflow: https://github.com/OmniNode-ai/omnibase_infra/actions/runs/33314493673

Test plan

  • CI passes (lockfile resolution is valid)
  • Downstream tests pass with the new dependency version

Evidence-Ticket: OMN-16997
Evidence-Source: OCC#7775

@jonahgabriel
jonahgabriel changed the base branch from main to dev August 30, 2026 23:40
@jonahgabriel jonahgabriel changed the title chore(deps): bump omnibase-infra to 0.38.14 chore(OMN-16997): bump omnibase-infra to 0.38.14 Aug 31, 2026
@onexbot-occ-writer

Copy link
Copy Markdown
Contributor Author

No OCC evidence companion was minted for this PR.

this PR is already bound to OCC#7682; its evidence companion exists and nothing needs authoring

To clear this: Nothing to do — the companion already exists.

Reported by node_occ_companion_effect (decline code already_bound, OMN-16665). This decision was made against the PR's LIVE state at compute time, not at publish time — a green publisher job only means the command reached the broker.

@jonahgabriel
jonahgabriel merged commit 2af6ed4 into dev Aug 31, 2026
53 of 54 checks passed
@jonahgabriel
jonahgabriel deleted the automation/bump-omnibase-infra-0.38.14 branch August 31, 2026 01:11
jonahgabriel pushed a commit to OmniNode-ai/onex_change_control that referenced this pull request Aug 31, 2026
…imemory#464 (#7775)

* evidence(OMN-16997): author OCC companion for OmniNode-ai/omnimemory#464

OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 250cc5d931e3840ad318a0079df35994419bea4b.

* evidence(OMN-16997): self-bind OCC#7775 + rebind contract_sha256

---------

Co-authored-by: omnimarket-bot <bot@omninode.ai>
jonahgabriel added a commit that referenced this pull request Aug 31, 2026
…pattern fixes (#470)

omnimemory#466 (OMN-17236) fixed three PII detector pattern defects on a live
persistence path and merged to dev at 2026-08-30T17:50:52Z. The v0.18.0 tag and
PyPI publish had already happened at 14:06Z that day, so the fixes missed the
cut by under four hours and there has been no release since.

The consequence is live and reproducible in the .201 dev lane, whose containers
all report omninode-memory 0.18.0:

    docker exec omninode-runtime python -c "... PIIDetector().detect_pii(s) ..."
    visa     -> 'card ***-***-****111111 end'   types: ['phone']
    discover -> 'card ***-***-****111117 end'   types: ['phone']
    uuid     -> 'run 550e8400-e29b-41d4-a***-***-****40000 done'
    ssn-sp   -> 'ssn 123 45 6789 end'           types: []

The trailing six digits of a Visa or Discover card are still being written into
stored content, UUID-bearing storage requests are still refused, and a
space-separated SSN is still not detected at all.

This bump is the first of three links; the omnimarket repin (exact pin at
==0.18.0) and the dev-lane image rebuild follow on OMN-17390.

Release contents (v0.18.0..dev): #466 PII fixes + 170 behavioral tests,
#467 all 14 Dependabot alerts, #464 omnibase-infra 0.38.14, #468 sibling locks,
#469 CI guide doc fix.
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