Maintenanceprompt onlyMedium

Upgrade Framework Version

This loop automates the process of upgrading a project's framework to a newer version. It systematically analyzes the current framework, plans the upgrade path, updates dependencies, resolves breaking changes, and ensures all tests pass before completion.

← all loops
upgradeframeworkmigrationbuild-test

Goal

Complete framework migration

How to Run

This loop guides you through upgrading your framework version with automated checks. It will incrementally update the framework, handle breaking changes, and verify stability at each step.

  1. 01

    Configure Your Tool

    Ensure your coding agent (Cursor, Claude Code, etc.) is set up to accept and process prompts.

  2. 02

    Run the Loop

    Execute this loop in your preferred environment. The agent will generate and execute prompts to perform the upgrade.

  3. 03

    Follow Prompts

    Respond to each prompt generated by the agent to complete the upgrade process.

Workflow Steps

  1. 01

    Analyze Current Framework

    Identify the current framework version and assess its usage in the codebase.

  2. 02

    Plan Upgrade Path

    Determine the target framework version and outline necessary steps for migration.

  3. 03

    Update Dependencies

    Modify package.json, pom.xml, or other dependency files to reflect the new framework version.

  4. 04

    Address Breaking Changes

    Refactor code to accommodate API changes, deprecations, and new patterns introduced in the target version.

  5. 05

    Test and Validate

    Run the full test suite to ensure the application works correctly with the upgraded framework.

  6. 06

    Resolve Issues

    Fix any failing tests or compatibility issues identified during validation.

Kickoff Prompt

Start the "Upgrade Framework Version" loop.

Goal: Complete framework migration
Max iterations: 10
Between iterations run: build and test
Exit when: Build and tests pass


Begin by checking the current framework version and dependencies. Analyze the codebase to identify potential breaking changes that may occur during the upgrade. Generate a plan for migrating to the target framework version while preserving existing functionality.

Self-pace this loop. After each iteration, run `build and test` and evaluate the output, and only continue if the exit condition is not met (Build and tests pass). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.

Guardrails

hardcoded
  • ·Do not introduce breaking changes without addressing them explicitly
  • ·Ensure all dependencies are compatible with the target framework version
  • ·Preserve existing application functionality during the upgrade
  • ·Validate that all tests pass before proceeding to the next step
  • ·Document any configuration changes made during the migration

Flow Diagram

rendering…

Related loops — Maintenance