Tasks

Upgrade the SDK

Move your app to a newer Rendel SDK, with every edit a breaking change asks for, in one prompt.

A release you want is out. The latest are Flutter 0.46.3 and Web 0.23.4; the changelog says what each brings.

Prompt

Upgrade the Rendel (rendel.ai) SDK in this project to {version}. I am the developer and I am asking for this. For Flutter it is a git dependency on https://github.com/neon-apps/rendel-flutter in pubspec.yaml: change its ref to the tag v{version} and run flutter pub get. For a website it is the script from https://rendel.ai/sdk/web/: change the version folder in its address to {version}. Read what changed between our version and {version} at https://rendel.ai/docs/reference/changelog and make every edit it says a break needs. Build the app and run its tests, then tell me what changed for us.

Paste into your coding agent, opened in your project. Works in Claude Code, Cursor, Codex, Windsurf, GitHub Copilot and Gemini CLI.

What the agent will do

  • Flutter: move the git dependency's ref to the new tag and run flutter pub get. Web: change the version folder in the script's address.
  • Read the changelog between your version and the new one, and make every edit it lists for a break.
  • Build and run your tests.

How to check it worked

Run the app once. Overview's Health shows the new version under SDK (for example Flutter 0.46.3 · iOS) once the build calls in.

Reference: what it writes
pubspec.yaml
  rendel:
    git:
      url: https://github.com/neon-apps/rendel-flutter.git
      ref: v0.46.3
Web
<script src="https://rendel.ai/sdk/web/0.23.4/rendel.js" data-app-key="rd_pk_…"></script>

Replace {version} with the version you want, such as 0.46.3 for Flutter or 0.23.4 for the web.

What to expect

Before 1.0.0 a minor version may break the public API; every break is in the changelog with the line to change, and the agent reads it for you. The wire protocol and the component catalog only grow, so an older build keeps working while you upgrade: the server never offers a build a component it does not know. Nothing in the console needs to change for an upgrade.

A web version stays pinned until you change the number, so your site changes only when you do.

Test as a real user

Create a test user from the Test page and talk as them, or pair a debug build and watch it from the console.

Fix a hidden launcher

The copilot's button does not show, or opening it draws nothing. One prompt finds the cause.

On this page

What to expect