Repository navigation
Specify exactly where package.json files are located - #9345
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Set npm update directories .github/dependabot.yml |
The npm update configuration now uses directories: ["wasm/*"] instead of directory: /. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Suggested reviewers: shaharnaveh
Merge Risk: 
Minimal · up to b5115
-
Dependabot is configured to scan every package directory in the repository.
Pre-merge checks: 
5
-
Full details: Title check
-
Explanation
The title "Specify exactly where package.json files are located" matches the changeset. The raw summary shows the npm Dependabot configuration in .github/dependabot.yml now targets the wasm/* directories instead of the repository root, which directly addresses the stated objective of telling Dependabot where package.json files live. The title is specific and describes the main change from the developer's perspective. No web search was needed for this check.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
|
@coderabbitai Will this change fix the problem of Dependabot not finding the |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain
The npm entry in
GitHub documents wildcard support for I verified the paths and configuration, but I have not observed a Dependabot run. After merging, check the next npm update-job log to confirm successful discovery. The weekly schedule and cooldown can delay update PRs even when discovery succeeds. You are interacting with an AI system. |
|
Thanks!! |
Integrate main at 9bd84b2 while preserving the published mega history. Keep the authentic profiler locator and capabilities from RustPython#9340, set-cycle GC from RustPython#9343, backward-compatible bytecode tooling from RustPython#9344, package paths from RustPython#9345, canonical Levenshtein coverage from RustPython#9346, and the safe full-width None-return scanner from RustPython#9347. Regenerate support helpers through the official updater from unchanged CPython d220409a13b7, preserving four exact existing-main neighborhoods. Retain the newer main specialization/C-stack helpers, Cargo environment adaptation, prior isolation checks and remaining Python 3.15 updates. The obsolete manual capability guard is superseded by the genuine API. Preserve unlanded explicit sharing modes and opcode override support. Ruff and XML vendor sources remain unchanged. Validation: normal hooks, locked host_env/VM/stdlib library check and strict Clippy, and the default CLI build. No target-runtime or full-suite pass is claimed for this composition. Assisted-by: OpenAI Codex:model version unavailable
One of checkbox below must be checked.
Summary
Dependabot keeps failing to find NPM updates because it expects a
package.jsonfile at the root of the repository. We don't structure RustPython like that, so I told Dependabot where to look forpackage.jsonfiles.Summary by CodeRabbit
wasmdirectories instead of the repository root.