Skip to content

GitHub App · early access

Find retiring AI model IDs and API versions in your code, before the shutdown date

Provider notices tell you which model is retiring. SunsetLint is being built to tell you where it is: the file and line in each repository, next to the shutdown date and the replacement the provider recommends.

The next deadline

Anthropic announced on 30 September 2026 that Claude Sonnet 4.5 retires on 30 November 2026. Source: Anthropic model deprecations, last verified 6 October 2026.
StatusIdentifierProviderDateDetails
RetiringClaude Sonnet 4.5Anthropic30 Nov 2026What to change
SunsetAssistants APIOpenAI26 Aug 2026Find leftover calls
Rejected (HTTP 400)temperature / top_p / top_kAnthropic, Claude 4.7+In effectWhy it breaks

Why a scanner, not another feed

Emails name the model, not the file

Provider emails go to the account owner. They don't say which service, cron job or notebook still uses the old ID.

Notice is short

Anthropic's 2026 retirement notices gave about 60 to 62 days, the policy minimum. In 2025 they gave about 4 to 6 months.

Package bots don't see call sites

Renovate and Dependabot work on package versions. A model string or a removed request parameter isn't a package.

Platforms have their own dates

Bedrock and Vertex set their own retirement dates, which can differ from the model maker's.

No code to an AI model

Matching is plain rules: literal strings and patterns. Your code is never sent to an LLM.

If a feed is enough, use a feed

deprecations.info is a free feed of AI model shutdowns. SunsetLint is for teams that want findings in their repos.

How it will work

The App is in early access. This is the design we are building toward; details may change before launch.
  1. 1

    Install on your GitHub org

    Pick all repositories or a few. The App asks for read-only access to contents and cannot change code.
  2. 2

    Scan against verified rules

    Each rule is an identifier pattern with the provider's shutdown date, the replacement and a link to the notice. A person checks each rule before it ships.
  3. 3

    One issue per repository

    A rolling issue lists file:line, identifier, shutdown date, replacement and source. It updates as you fix things.
  4. 4

    Checks on pull requests (Pro)

    A Check Run annotates pull requests that add a new reference to a retiring identifier, so old IDs don't creep back in.

What it doesn't do

  • It doesn't open pull requests or edit code. It has no write access to contents.
  • It doesn't guarantee complete coverage. It checks your code against the rules we have verified, and each rule links to its source.
  • It doesn't support GitLab or Bitbucket.

Get early access to the GitHub App

SunsetLint is in early access. Join the list and we'll send an install invite when the App opens to your org.