Skip to content

chore: Configure Renovate - #1

Merged
ScriptedAlchemy merged 1 commit into
mainfrom
renovate/configure
Nov 6, 2025
Merged

ScriptedAlchemy merged 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Nov 5, 2025 •

Copy link
Copy Markdown
Contributor

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • codex-rs/Cargo.toml (cargo)
  • codex-rs/ansi-escape/Cargo.toml (cargo)
  • codex-rs/app-server-protocol/Cargo.toml (cargo)
  • codex-rs/app-server/Cargo.toml (cargo)
  • codex-rs/apply-patch/Cargo.toml (cargo)
  • codex-rs/arg0/Cargo.toml (cargo)
  • codex-rs/async-utils/Cargo.toml (cargo)
  • codex-rs/backend-client/Cargo.toml (cargo)
  • codex-rs/chatgpt/Cargo.toml (cargo)
  • codex-rs/cli/Cargo.toml (cargo)
  • codex-rs/cloud-tasks-client/Cargo.toml (cargo)
  • codex-rs/cloud-tasks/Cargo.toml (cargo)
  • codex-rs/codex-backend-openapi-models/Cargo.toml (cargo)
  • codex-rs/common/Cargo.toml (cargo)
  • codex-rs/core/Cargo.toml (cargo)
  • codex-rs/exec/Cargo.toml (cargo)
  • codex-rs/execpolicy/Cargo.toml (cargo)
  • codex-rs/feedback/Cargo.toml (cargo)
  • codex-rs/file-search/Cargo.toml (cargo)
  • codex-rs/keyring-store/Cargo.toml (cargo)
  • codex-rs/linux-sandbox/Cargo.toml (cargo)
  • codex-rs/login/Cargo.toml (cargo)
  • codex-rs/mcp-server/Cargo.toml (cargo)
  • codex-rs/mcp-types/Cargo.toml (cargo)
  • codex-rs/ollama/Cargo.toml (cargo)
  • codex-rs/otel/Cargo.toml (cargo)
  • codex-rs/process-hardening/Cargo.toml (cargo)
  • codex-rs/protocol-ts/Cargo.toml (cargo)
  • codex-rs/protocol/Cargo.toml (cargo)
  • codex-rs/responses-api-proxy/Cargo.toml (cargo)
  • codex-rs/rmcp-client/Cargo.toml (cargo)
  • codex-rs/stdio-to-uds/Cargo.toml (cargo)
  • codex-rs/tui/Cargo.toml (cargo)
  • codex-rs/utils/cache/Cargo.toml (cargo)
  • codex-rs/utils/git/Cargo.toml (cargo)
  • codex-rs/utils/image/Cargo.toml (cargo)
  • codex-rs/utils/json-to-toml/Cargo.toml (cargo)
  • codex-rs/utils/pty/Cargo.toml (cargo)
  • codex-rs/utils/readiness/Cargo.toml (cargo)
  • codex-rs/utils/tokenizer/Cargo.toml (cargo)
  • codex-rs/windows-sandbox-rs/Cargo.toml (cargo)
  • sdk/native/Cargo.toml (cargo)
  • .devcontainer/Dockerfile (dockerfile)
  • codex-cli/Dockerfile (dockerfile)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/codespell.yml (github-actions)
  • .github/workflows/issue-deduplicator.yml (github-actions)
  • .github/workflows/issue-labeler.yml (github-actions)
  • .github/workflows/rust-ci.yml (github-actions)
  • .github/workflows/rust-release.yml (github-actions)
  • .github/workflows/sdk.yml (github-actions)
  • sdk/native/.github/workflows/CI.yml (github-actions)
  • codex-cli/package.json (npm)
  • codex-rs/responses-api-proxy/npm/package.json (npm)
  • package.json (npm)
  • pnpm-workspace.yaml (npm)
  • sdk/native/package.json (npm)
  • sdk/typescript/package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 55 Pull Requests:

chore(deps): update taiki-e/install-action digest to 6f9c7cc
  • Schedule: ["at any time"]
  • Branch name: renovate/taiki-e-install-action-digest
  • Merge into: main
  • Upgrade taiki-e/install-action to 6f9c7cc51aa54b13cbcbd12f8bbf69d8ba405b4b
chore(deps): update dependency @​types/node to v20.19.24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 20.19.24
chore(deps): update dependency ts-jest to v29.4.5
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-jest-29.x-lockfile
  • Merge into: main
  • Upgrade ts-jest to 29.4.5
chore(deps): update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: main
  • Upgrade typescript to 5.9.3
chore(deps): update rust crate arboard to v3.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/arboard-3.x-lockfile
  • Merge into: main
  • Upgrade arboard to 3.6.1
chore(deps): update rust crate axum to v0.8.6
  • Schedule: ["at any time"]
  • Branch name: renovate/axum-monorepo
  • Merge into: main
  • Upgrade axum to 0.8.6
chore(deps): update rust crate clap to v4.5.51
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x-lockfile
  • Merge into: main
  • Upgrade clap to 4.5.51
chore(deps): update rust crate clap_complete to v4.5.60
  • Schedule: ["at any time"]
  • Branch name: renovate/clap_complete-4.x-lockfile
  • Merge into: main
  • Upgrade clap_complete to 4.5.60
chore(deps): update rust crate ignore to v0.4.25
  • Schedule: ["at any time"]
  • Branch name: renovate/ignore-0.x-lockfile
  • Merge into: main
  • Upgrade ignore to 0.4.25
chore(deps): update rust crate landlock to v0.4.3
  • Schedule: ["at any time"]
  • Branch name: renovate/landlock-0.x-lockfile
  • Merge into: main
  • Upgrade landlock to 0.4.3
chore(deps): update rust crate libc to v0.2.177
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x-lockfile
  • Merge into: main
  • Upgrade libc to 0.2.177
chore(deps): update rust crate openssl-sys to v0.9.110
  • Schedule: ["at any time"]
  • Branch name: renovate/openssl-sys-0.x-lockfile
  • Merge into: main
  • Upgrade openssl-sys to 0.9.110
chore(deps): update rust crate owo-colors to v4.2.3
  • Schedule: ["at any time"]
  • Branch name: renovate/owo-colors-4.x-lockfile
  • Merge into: main
  • Upgrade owo-colors to 4.2.3
chore(deps): update rust crate regex-lite to v0.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/regex-lite-0.x-lockfile
  • Merge into: main
  • Upgrade regex-lite to 0.1.8
chore(deps): update rust crate reqwest to v0.12.24
  • Schedule: ["at any time"]
  • Branch name: renovate/reqwest-0.x-lockfile
  • Merge into: main
  • Upgrade reqwest to 0.12.24
chore(deps): update rust crate rmcp to v0.8.5
  • Schedule: ["at any time"]
  • Branch name: renovate/rmcp-0.x-lockfile
  • Merge into: main
  • Upgrade rmcp to 0.8.5
chore(deps): update rust crate tokio-util to v0.7.17
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-util-0.x-lockfile
  • Merge into: main
  • Upgrade tokio-util to 0.7.17
chore(deps): update rust crate toml to v0.9.8
  • Schedule: ["at any time"]
  • Branch name: renovate/toml-0.x-lockfile
  • Merge into: main
  • Upgrade toml to 0.9.8
chore(deps): update rust crate toml_edit to v0.23.7
  • Schedule: ["at any time"]
  • Branch name: renovate/toml_edit-0.x-lockfile
  • Merge into: main
  • Upgrade toml_edit to 0.23.7
chore(deps): update rust crate unicode-width to v0.2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/unicode-width-0.x-lockfile
  • Merge into: main
  • Upgrade unicode-width to 0.2.2
chore(deps): update rust crate url to v2.5.7
  • Schedule: ["at any time"]
  • Branch name: renovate/url-2.x-lockfile
  • Merge into: main
  • Upgrade url to 2.5.7
chore(deps): update rust crate webbrowser to v1.0.6
  • Schedule: ["at any time"]
  • Branch name: renovate/webbrowser-1.x-lockfile
  • Merge into: main
  • Upgrade webbrowser to 1.0.6
chore(deps): update rust crate zeroize to v1.8.2
  • Schedule: ["at any time"]
  • Branch name: renovate/zeroize-1.x-lockfile
  • Merge into: main
  • Upgrade zeroize to 1.8.2
chore(deps): update cross-platform-actions/action action to v0.30.0
  • Schedule: ["at any time"]
  • Branch name: renovate/cross-platform-actions-action-0.x
  • Merge into: main
  • Upgrade cross-platform-actions/action to v0.30.0
chore(deps): update dependency @​modelcontextprotocol/sdk to v1.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/modelcontextprotocol-sdk-1.x-lockfile
  • Merge into: main
  • Upgrade @modelcontextprotocol/sdk to 1.21.0
chore(deps): update dependency @​openai/agents to ^0.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/openai-agents-0.x
  • Merge into: main
  • Upgrade @openai/agents to ^0.3.0
chore(deps): update dependency eslint to v9.39.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 9.39.1
chore(deps): update dependency prettier to v3.6.2
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.6.2
chore(deps): update dependency typescript-eslint to v8.46.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.46.3
chore(deps): update opentelemetry-rust monorepo to 0.31.0
chore(deps): update pnpm to v10.20.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.20.0
chore(deps): update rust crate askama to 0.14
  • Schedule: ["at any time"]
  • Branch name: renovate/askama-0.x
  • Merge into: main
  • Upgrade askama to 0.14
chore(deps): update rust crate assert_cmd to v2.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/assert_cmd-2.x-lockfile
  • Merge into: main
  • Upgrade assert_cmd to 2.1.1
chore(deps): update rust crate crossterm to 0.29.0
  • Schedule: ["at any time"]
  • Branch name: renovate/crossterm-0.x
  • Merge into: main
  • Upgrade crossterm to 0.29.0
chore(deps): update rust crate ctor to 0.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ctor-0.x
  • Merge into: main
  • Upgrade ctor to 0.6.0
chore(deps): update rust crate lru to 0.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lru-0.x
  • Merge into: main
  • Upgrade lru to 0.16.0
chore(deps): update rust crate pulldown-cmark to 0.13
  • Schedule: ["at any time"]
  • Branch name: renovate/pulldown-cmark-0.x
  • Merge into: main
  • Upgrade pulldown-cmark to 0.13
chore(deps): update rust crate regex to v1.12.2
  • Schedule: ["at any time"]
  • Branch name: renovate/regex-1.x-lockfile
  • Merge into: main
  • Upgrade regex to 1.12.2
chore(deps): update rust crate schemars to 0.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/schemars-0.x
  • Merge into: main
  • Upgrade schemars to 0.9.0
chore(deps): update rust crate serde_with to v3.15.1
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_with-3.x-lockfile
  • Merge into: main
  • Upgrade serde_with to 3.15.1
chore(deps): update rust crate tokio to v1.48.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: main
  • Upgrade tokio to 1.48.0
chore(deps): update rust crate tonic to 0.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tonic-monorepo
  • Merge into: main
  • Upgrade tonic to 0.14.0
chore(deps): update rust crate ts-rs to v11.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-rs-11.x-lockfile
  • Merge into: main
  • Upgrade ts-rs to 11.1.0
fix(deps): update rust crate core-foundation to 0.10
  • Schedule: ["at any time"]
  • Branch name: renovate/core-foundation-0.x
  • Merge into: main
  • Upgrade core-foundation to 0.10
fix(deps): update rust crate rand to 0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.x
  • Merge into: main
  • Upgrade rand to 0.9
fix(deps): update rust crate sentry to v0.45.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sentry-rust-monorepo
  • Merge into: main
  • Upgrade sentry to 0.45
  • Upgrade sentry to 0.45.0
fix(deps): update rust crate windows-sys to 0.61
  • Schedule: ["at any time"]
  • Branch name: renovate/windows-sys-0.x
  • Merge into: main
  • Upgrade windows-sys to 0.61
chore(deps): update actions/download-artifact action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/download-artifact to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency eslint-config-prettier to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-10.x
  • Merge into: main
  • Upgrade eslint-config-prettier to ^10.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
  • Upgrade @types/node to ^24.0.0
chore(deps): update dependency zod to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/zod-4.x
  • Merge into: main
  • Upgrade zod to ^4.0.0
chore(deps): update jest monorepo to v30 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade @jest/globals to ^30.0.0
  • Upgrade @types/jest to ^30.0.0
  • Upgrade jest to ^30.0.0
chore(deps): update rust crate schemars to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/schemars-1.x
  • Merge into: main
  • Upgrade schemars to 1.0.0
chore(deps): update rust crate which to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/which-8.x
  • Merge into: main
  • Upgrade which to 8

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

  • Failed to look up npm package @codex-native/sdk-darwin-arm64
  • Failed to look up npm package @codex-native/sdk-darwin-x64
  • Failed to look up npm package @codex-native/sdk-linux-arm64-gnu
  • Failed to look up npm package @codex-native/sdk-linux-arm64-musl
  • Failed to look up npm package @codex-native/sdk-linux-x64-gnu
  • Failed to look up npm package @codex-native/sdk-linux-x64-musl
  • Failed to look up npm package @codex-native/sdk-win32-arm64-msvc
  • Failed to look up npm package @codex-native/sdk-win32-x64-msvc

Files affected: sdk/native/package.json


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Nov 5, 2025 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 4b25a3c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Nov 5, 2025

Copy link
Copy Markdown
Contributor


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@ScriptedAlchemy
ScriptedAlchemy force-pushed the renovate/configure branch 4 times, most recently from 11db8b4 to e5b1911 Compare November 6, 2025 01:59
@ScriptedAlchemy
ScriptedAlchemy merged commit 52fc9dd into main Nov 6, 2025
1 of 4 checks passed
@renovate
renovate Bot deleted the renovate/configure branch November 6, 2025 02:10
@ScriptedAlchemy

Copy link
Copy Markdown
Owner

@dependabot recreate

ScriptedAlchemy pushed a commit that referenced this pull request Jan 12, 2026
Agent wouldn't "see" attached images and would instead try to use the
view_file tool:
<img width="1516" height="504" alt="image"
src="https://github.com/user-attachments/assets/68a705bb-f962-4fc1-9087-e932a6859b12"
/>

In this PR, we wrap image content items in XML tags with the name of
each image (now just a numbered name like `[Image #1]`), so that the
model can understand inline image references (based on name). We also
put the image content items above the user message which the model seems
to prefer (maybe it's more used to definitions being before references).

We also tweak the view_file tool description which seemed to help a bit

Results on a simple eval set of images:

Before
<img width="980" height="310" alt="image"
src="https://github.com/user-attachments/assets/ba838651-2565-4684-a12e-81a36641bf86"
/>

After
<img width="918" height="322" alt="image"
src="https://github.com/user-attachments/assets/10a81951-7ee6-415e-a27e-e7a3fd0aee6f"
/>

```json
[
  {
    "id": "single_describe",
    "prompt": "Describe the attached image in one sentence.",
    "images": ["image_a.png"]
  },
  {
    "id": "single_color",
    "prompt": "What is the dominant color in the image? Answer with a single color word.",
    "images": ["image_b.png"]
  },
  {
    "id": "orientation_check",
    "prompt": "Is the image portrait or landscape? Answer in one sentence.",
    "images": ["image_c.png"]
  },
  {
    "id": "detail_request",
    "prompt": "Look closely at the image and call out any small details you notice.",
    "images": ["image_d.png"]
  },
  {
    "id": "two_images_compare",
    "prompt": "I attached two images. Are they the same or different? Briefly explain.",
    "images": ["image_a.png", "image_b.png"]
  },
  {
    "id": "two_images_captions",
    "prompt": "Provide a short caption for each image (Image 1, Image 2).",
    "images": ["image_c.png", "image_d.png"]
  },
  {
    "id": "multi_image_rank",
    "prompt": "Rank the attached images from most colorful to least colorful.",
    "images": ["image_a.png", "image_b.png", "image_c.png"]
  },
  {
    "id": "multi_image_choice",
    "prompt": "Which image looks more vibrant? Answer with 'Image 1' or 'Image 2'.",
    "images": ["image_b.png", "image_d.png"]
  }
]
```
regexyl pushed a commit to regexyl/codex-native that referenced this pull request Feb 2, 2026
I've seen this test fail with:

```
 - Mock ScriptedAlchemy#1.
        	Expected range of matching incoming requests: == 2
        	Number of matched incoming requests: 1
```

This is because we pop the wrong task_complete events and then the test
exits. I think this is because the MCP events are now buffered after
openai/codex#8874.

So:
1. clear the buffer before we do any user message sending
2. additionally listen for task start before task complete
3. use the ID from task start to find the correct task complete event.
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