chore(deps): bump mcp from 1.27.0 to 1.28.1 in /envs/grid_world_env

[dependabot]

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Note

Low Risk
Lockfile-only dependency resolution with a minor mcp patch bump; no runtime code changes in this diff.

Overview
Refreshes envs/grid_world_env/uv.lock so Dependabot’s mcp bump from 1.27.0 to 1.28.1 is recorded, with no changes to application source in this PR.

The lockfile also moves every resolved package from the Hugging Face PyPI registry to https://pypi.org/simple, bumps the lock revision to 3, and updates the editable openenv entry in the lock from 0.3.2.dev0 to 0.4.2.dev0 as part of the same resolution pass.

^{Reviewed by Cursor Bugbot for commit 0051b08. Bugbot is set up for automated code reviews on this repo. Configure here.}

[bot-ci-comment]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[cursor]

Alignment Review Report

Dependabot lock-only bump of the transitive mcp package (1.27.0 → 1.28.1) in envs/grid_world_env. Only envs/grid_world_env/uv.lock changed. Verdict: correct, security-positive, no blocking issues.

Automated Checks

• Lint: PASS (N/A to this PR) — the only changed file is uv.lock (ruff/usort don't lint .lock/TOML). lint.sh flags ~20 pre-existing ruff format candidates in other envs (opencode_env, chat_env, jupyter_env, …); none is grid_world_env, so the exit is not caused by this PR.
• Debug code: CLEAN — check-debug.sh only scans src/; all hits are pre-existing (src/openenv/cli/...), 0 matches in grid_world_env.

Open RFCs Context

• 003-mcp-support (In Review) is the nearest RFC but governs the MCP protocol/interface, not the pinned version of the mcp PyPI library. No RFC covers dependency management / PyPI index source → no RFC conflict.
• 000/001/002/005 (In Review) and 010 (Draft) are unrelated to a transitive lock bump.

Tier 1: Fixes Required

None. (Dependabot-generated lockfile; the registry-source choice is a team decision — flag, don't edit.)

Tier 2: Alignment Discussion

Principle Conflicts

ALIGNMENT FLAG: Lockfile package index silently flipped from the HF internal mirror to public PyPI

• Principle at stake: "Container isolation for reproducibility and security" (PRINCIPLES.md:15)
• The concern: re-locking rewrote all 115 source = { registry = "https://pypi.registries.huggingface.tech/" } entries to https://pypi.org/simple (0 mirror refs remain). Artifact URLs stay on files.pythonhosted.org and all hashes are unchanged, so this is very likely benign, but it changes the declared provenance of every package and widens a mirror-vs-PyPI split across envs. This is a recurring side effect of native dependabot env-lock PRs.
• Suggested reviewer: @Darktex (authored the reproducibility principle) + @burtenshaw (owns dependabot config)

RFC Conflicts

None identified.

Verification performed (positive signals)

• Security fix (net positive): base mcp==1.27.0 carries two advisories — GHSA-hvrp-rf83-w775 (CVE-2026-52870) and GHSA-jpw9-pfvf-9f58 (CVE-2026-52869), both fixed_in: 1.27.2. 1.28.1 clears both (0 known vulns on PyPI).
• Correct scope: mcp is transitive (openenv>=0.2.2 → fastmcp → mcp; no mcp pin in pyproject) → lock-only bump with no pyproject edit is correct.
• Lock consistency: uv lock --check --project envs/grid_world_env passes (117 pkgs). Package set 117→117, 0 added/removed; only mcp and openenv changed version.
• Hashes verified live vs PyPI: sdist d51e36a5…69683 (638501) and wheel 2726bca5…991df (222620) both match the lock; not yanked; requires-python >=3.10 satisfied by the env's >=3.12.
• Benign extra change: openenv 0.3.2.dev0 → 0.4.2.dev0 is just the editable local path dep ({ editable = "../../" }) refreshing to the current root version (pyproject.toml = 0.4.2.dev0); openenv>=0.2.2 floor still satisfied. Also revision 2→3 (13 envs already on rev 3).
• Deploy note (informational): grid_world_env/server/Dockerfile installs via pip install -r requirements.txt + COPY src/openenv/core/, not uv sync --frozen, so this env's container build does not consume uv.lock — the index-flip / revision bump / mcp version here affect local dev only, not the deployed image.

Process note (non-blocking, cc @burtenshaw)

.github/dependabot.yml configures the uv updater with directory: "/" + exclude-paths: ["envs/**"], yet this native dependabot/uv/envs/grid_world_env/... PR still edited envs/grid_world_env/uv.lock. exclude-paths is a valid Dependabot key but the uv ecosystem doesn't appear to honor it; the codex/dependabot-envs-* aggregate roll-ups are the intended path for env locks. Not a code issue with this PR.

Summary

• 0 mechanical issues to fix
• 1 alignment point for human review (index-flip → reproducibility) + 1 process note
• 0 RFC conflicts

  

_{Sent by Cursor Automation: Pre-review}

[cursor]

mcp 1.27.0 → 1.28.1 — security-positive. Base 1.27.0 is vulnerable to two advisories, both fixed_in: 1.27.2:

• GHSA-hvrp-rf83-w775 / CVE-2026-52870 (experimental task handlers lack session-ownership checks)
• GHSA-jpw9-pfvf-9f58 / CVE-2026-52869 (SSE / Streamable-HTTP session routed by session-id alone)

1.28.1 (> 1.27.2) clears both (0 known vulns on PyPI). mcp is transitive via openenv → fastmcp (no pin in pyproject), so this lock-only bump is correct. uv lock --check passes (117 pkgs; set unchanged, only mcp + the editable openenv version refreshed).

[cursor]

Artifact hashes verified live against PyPI: sdist sha256:d51e36a5…69683 (size 638501) and wheel sha256:2726bca5…991df (size 222620) both match this lock. Not yanked; requires-python >=3.10 is satisfied by the env's requires-python >=3.12.

[cursor]

Tier 2 (reproducibility): the re-lock flipped every package's index source from the HF mirror https://pypi.registries.huggingface.tech/ to https://pypi.org/simple — all 115 entries (0 mirror refs remain). Artifact URLs (files.pythonhosted.org) and hashes are unchanged, so this is likely benign, but it changes declared provenance and widens the mirror-vs-PyPI split across envs. Registry choice is a team decision — flag, not auto-fix. cc @Darktex @burtenshaw (PRINCIPLES.md:15).

[cursor]

Lock revision 2 → 3 (13 envs are already on rev 3, so low risk). Note for this env specifically: server/Dockerfile installs via pip install -r requirements.txt + COPY src/openenv/core/, not uv sync --frozen, so uv.lock isn't consumed by the container build — the revision bump has no deploy impact here.

[burtenshaw]

Aggregated into #921.

[dependabot]

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.