Blog

Fix retiring AI model IDs with one pull request

17 November 2026 · Driftline

Driftline's GitHub Action can now make the change for you. Add fix-pr: true and it opens one draft pull request that swaps retiring model IDs for their replacements. Lines where a new name isn't enough get a checklist with what to change and a link to the provider's guide. With Driftline Pro, the same pull request shows how your real prompts answer on the new model.

What the pull request contains

There is one pull request, on the branch driftline/model-updates. Later runs rebuild it from your default branch and update it, and Driftline closes it once nothing is left to rename. It never touches documentation files or your prompt file.

Set it up

Add a scheduled workflow, for example every Monday:

# .github/workflows/driftline.yml
on:
  schedule: [{ cron: "0 6 * * 1" }]
  workflow_dispatch:
permissions:
  contents: write
  pull-requests: write
jobs:
  driftline:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: AI-Driftline/driftline@v0
        with:
          fix-pr: true
          fail-on: never

Then turn on Settings → Actions → General → Allow GitHub Actions to create and approve pull requests in the repository. In an organization, turn it on in the organization's settings first, or the option is greyed out. If it is off, Driftline still pushes the branch and tells you which setting to change.

Pull requests opened with the default workflow token don't start your other workflows, which is GitHub's rule. If your tests should run on Driftline's pull request, pass a personal access token as github-token.

Try it locally first

The same renames are available from the command line, with nothing to install:

npx -y @aidriftline/driftline fix --dry-run   # show what would change
npx -y @aidriftline/driftline fix             # change it

Why a rename isn't the whole job

A new model name keeps the API call working, but the new model can answer differently: a summary gets shorter, a label changes, or a JSON answer stops parsing. That's what the Pro drift test is for. It runs the 5 to 20 prompts your app really sends on both models, two API calls per prompt on your own key, and puts the result in the pull request. The answers themselves stay in the job summary, since anyone who can read the pull request would see them.

The scan, the fix command and the fix pull request are free. See an example pull request, or add the Action.