Since.dev
ChatGPT pluginWhat changed, and the fix
Catch breaking changes, deprecations, security advisories and retiring AI models in your dependencies before they break your code, and get the fix: file and line, days left, the pull request.
Since.dev is #13,702 of 13,927 ChatGPT plugins by placement.
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
1 listing change logged · latest Nov 15: Version. See what changed
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools1,035th of 1,065 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 1033 | #13689 | — | |
| 1034 | #13693 | — | |
| 1035 | #13702 | — | |
| 1036 | #13715 | — | |
| 1037 | #13800 | — |
Also on other marketplaces
Example prompts
- “Use Since.dev to list the OpenAI and Anthropic models new code should use today.”
- “Use Since.dev to check whether Node.js 18 and Python 3.9 are past end of life.”
- “Use Since.dev to show what changed in Next.js since version 14 that could break an upgrade.”
Skills
since-before-upgrading
Use before upgrading, adding or removing a dependency, before editing a manifest or lockfile (package.json, package-lock.json, requirements.txt, pyproject.toml, poetry.lock, go.mod, Cargo.toml, Gemfile, pom.xml, build.gradle, composer.json and the like), and when a build breaks after a version bump. Asks Since.dev what the change breaks in this code, with the file and line, how severe it is, the days left and what to move to.
since-ci-and-runtimes
Use when editing CI workflows (.github/workflows/*.yml), Dockerfiles, docker-compose files or runtime version files (.nvmrc, .node-version, .python-version, .tool-versions, go.mod, global.json), when choosing a runtime or base image version, and when a CI runner or image fails. Asks Since.dev which runner images, base images and runtime versions are past or near end of life, and what to move to.
since-model-retirements
Use whenever code names an AI model ID (for example gpt-5, gpt-4o-mini-2024-07-18, claude-sonnet-4-5-20250929, gemini-2.5-pro, or a Bedrock, Vertex AI or Azure model ID), when choosing or switching a model, and when a model call starts failing with a model-not-found error. Asks Since.dev whether the model is deprecated or retiring, on which date on the platform the code calls, and what replaces it.
since-what-changed
Use before writing code against a library, SDK, framework, API or runtime you learned about in training, especially fast-moving ones, and when the user asks what changed in a package, provider, model or API since a date or version. Asks Since.dev what changed after your training cutoff, so the code matches the versions that exist today.
- Categories
- Sign-in
- On Install
- Capabilities
- Read, Write
- Availability
- Available
- Version
- 4.4.0
- Keywords
- mcp, dependencies, breaking-changes, deprecations, changelog, upgrades, migrations, security-advisories, vulnerabilities, end-of-life, ai-models, model-deprecation, model-retirement, npm, pypi, github-actions
- Created
- November 10, 2026
- More info
- Sponsorship
- Promote this plugin