← Since.devCONTENT HISTORY

Update to Since.dev

Snapshot Nov 12, 2026 · 00:10 UTC · version 4.3.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Since.dev and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "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.",
  "included_files": [],
  "name": "since-what-changed",
  "skill_md_contents": "---\nname: since-what-changed\ndescription: 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.\n---\n\n# Ask Since.dev what changed since you were trained\n\nYou learned these packages and APIs at a point in time. Since then, functions were renamed or removed, parameters changed, models retired and runtimes reached end of life. Since.dev keeps the record of every change, with its source, so you can catch up before you write code.\n\n## Catch up on one thing\n\nCall `whats_changed` with what you are about to use and `since` set to your training cutoff as a date:\n\n```json\n{ \"package\": \"pypi:openai\", \"since\": \"2025-01-01\" }\n```\n\nInstead of `package`, use `provider` (for example `stripe` or `anthropic`), `model`, or `surface` (an API host such as `api.stripe.com`, or a runtime such as `runtime:node@20`). Use a version instead of a date when you know which one the project has: `\"since\": \"1.40.0\"`.\n\nEach change gives its kind, severity, dates, the replacement and a link to the publisher's source. Page through more with `nextCursor`. To read one change in full, call `whats_changed` with its `id`.\n\n## Check the code you wrote\n\nAfter writing it, call `check_code` with the snippet and its language. It reports anything in the code that a recorded change affects, with the line.\n\n## Ask whether something is still supported\n\n```json\n{ \"surface\": \"runtime:python@3.9\" }\n```\n\nWith `check_code`, the answer says `supported`, `deprecated`, `retired` or `unknown`, with its source.\n\nTreat `needs_review` and `unknown` as not settled. When an answer cites a source, prefer it over what you remember.\n"
}

SHA-256 of public snapshot: b45cadc8513568614719921051b22c4b1ee3e25acad2efb63004aa1038dc12a4