Bump openai from 6.41.0 to 6.42.0 - #19
Merged
Merged
Conversation
Bumps [openai](https://github.com/openai/openai-node) from 6.41.0 to 6.42.0. - [Release notes](https://github.com/openai/openai-node/releases) - [Changelog](https://github.com/openai/openai-node/blob/main/CHANGELOG.md) - [Commits](openai/openai-node@v6.41.0...v6.42.0) --- updated-dependencies: - dependency-name: openai dependency-version: 6.42.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 18, 2026
Merged
BigSimmo added a commit
that referenced
this pull request
Jul 22, 2026
This was referenced Jul 23, 2026
This was referenced Jul 28, 2026
BigSimmo added a commit
that referenced
this pull request
Jul 28, 2026
* test(rag): offline regression guard for #19 comparison fallback Pin the conservative contract of the shipped #19 fix (source-bound admission/discharge comparison fallback, 2026-07-27) so a future change cannot silently reopen it. Currently that behaviour is covered only by the provider-backed canary; this adds a fast offline lock. buildAdmissionDischargeComparisonAnswer emits a two-sided comparison only when each side yields a source-bound requirement fact from a distinct document, otherwise returns null so the caller terminates at an evidence gap rather than fabricating a one-sided comparison. Guards: - both sides source-bound (distinct docs) -> cites BOTH documents - only one side source-bound -> null (intended evidence gap, not a drop) - both facts from the same physical document -> null (same-document trap) Adds a one-line export seam on buildAdmissionDischargeComparisonAnswer (additive; sibling helpers already exported for tests). Loosening the binders is the refuted approach that reopens #19 — these fail fast if a change moves that way. RAG impact: no retrieval behaviour change — test-only regression guard plus an additive export seam; zero logic, ranking, or ordering change. #19 stays resolved. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(ci): do not hard-fail Next build RAM guard under CI GitHub-hosted runners sometimes report ~7.8 GiB total RAM, which made scripts/guard-next-build.mjs exit before next build and flake the Build job. Keep the local/Docker hard-fail under 10 GiB; warn and continue when CI or GITHUB_ACTIONS is set. Add a focused unit test for the decision. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * docs(ledger): record PR #1307 CI babysit and Bugbot closeout Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * ci: sync PR #1307 policy body with Clinical Governance Preflight Temporary PR_POLICY_BODY.md so the Sync PR policy body job can apply the required Clinical Governance Preflight section (ManagePullRequest cannot edit this non-agent-managed description). Remove after sync succeeds. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * ci: remove PR_POLICY_BODY.md after sync The Sync PR policy body job applied the Clinical Governance Preflight section to PR #1307. Drop the temporary template so it cannot overwrite other PR descriptions if this branch merges. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * docs(ledger): note PR #1307 policy body sync and template removal Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix(ci): type the Next build RAM guard env as a partial stub Static PR typecheck failed because ProcessEnv requires NODE_ENV when tests passed `{}` / `{ CI }` stubs into evaluateNextBuildRamGuard. Accept a plain env record via options so CI stubs typecheck without a full ProcessEnv. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> * fix(ci): allow low-RAM Docker app builds via explicit build-arg Container images/app-image failed because Docker buildx runners report ~7.8 GiB and do not set CI inside the build stage, so the Next RAM guard still hard-failed. Accept ALLOW_LOW_RAM_BUILD=1 (passed only from the CI docker-image workflow); local Docker Desktop keeps the default hard-fail. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps openai from 6.41.0 to 6.42.0.
Release notes
Sourced from openai's releases.
Changelog
Sourced from openai's changelog.
Commits
6f849f4release: 6.42.0579edb2feat(api): responses.moderation and chat_completions.moderationDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)