Update Dependencies

Role: You are a coding agent. Explore the codebase, plan, execute, and verify. These instructions are harness-agnostic: they do not depend on Jules, Claude Code, Codex, Cursor, or any other product’s tool names.

Objective: Update the dependencies of this repository to their latest compatible versions while ensuring that all tests pass and the project remains stable.

Context:

• Key Files & Folders:
  • Package management file(s) (e.g., package.json, requirements.txt, pom.xml).
  • Lock file(s) (e.g., package-lock.json, yarn.lock, poetry.lock).
  • Test files and configuration (e.g., tests/, jest.config.js).
  • CI/CD configuration (e.g., .github/workflows/).

Requirements & Constraints:

• No Breaking Changes: You must not introduce any breaking changes to the project’s functionality.
• Tests Must Pass: All existing tests must pass after the dependency update.
• Application Stability: You must verify that the application or library builds and runs correctly after the update.

Guiding Principles:

• Baseline First: Before making any changes, run the full test suite to ensure the project is in a good state. If tests are failing on the base commit, report it and ask for guidance.
• Incremental Updates: Avoid updating all dependencies at once. If possible, update them in logical groups (e.g., minor versions first, then majors) or one by one for critical libraries. This makes it easier to identify the source of any new issues.
• Read the Changelogs: For major version updates, consult the changelogs or release notes for the libraries to understand potential breaking changes.
• Leverage Tooling: Use built-in package manager commands to check for outdated packages (e.g., npm outdated, pip list --outdated).
• Test Everything: After every significant change, run the relevant tests. After all dependencies are updated, run the entire test suite.

Execution Flow:

1. Explore & Plan:
   • Investigate the codebase to understand the project’s language, framework, and dependency management setup.
   • Identify the commands to install dependencies, run tests, and build the project.
   • Formulate a detailed, step-by-step plan for updating the dependencies, including establishing a baseline, updating, and verifying.
   • Write the plan. If the harness can pause for approval, wait; otherwise state the plan and proceed.
2. Execute & Verify:
   • Baseline: Run the test suite to confirm it’s clean.
   • Update: Use the package manager to update the dependencies.
   • Verify: After updating, run the tests again. If they fail, debug the issues. This may involve:
     • Checking for breaking changes in the updated libraries.
     • Pinning a problematic dependency to an older, compatible version.
     • Making necessary code changes to adapt to the new dependency versions.
3. Test & Review:
   • Once all dependencies are updated and all tests pass, perform a final check by building the project and running any end-to-end or integration tests if they exist.
   • Request a code review through the harness if it has one; otherwise include the review in the deliverable.
4. Submit:
   • Address any feedback from the code review.
   • Once the work is complete and verified, open a pull request (or the harness equivalent) with a title, a summary of what was verified, and a link to the original task.

Deliverables:

• A pull request with updated dependency files (package.json, package-lock.json, etc.).
• The pull request title should clearly state that dependencies have been updated.
• The pull request body should summarize the major changes and link to any relevant changelogs.