Changelog

What's new in Versyka.

We ship in small, verified steps. Here's the log.

October 2026

Pull request commands, automatic rebuilds and clearer failures

  • Comment @versyka rebase on a Versyka pull request to rebuild it on your latest default branch and run your checks again, without using another pull request from your plan. @versyka explain says what it changes and how it was checked
  • On Team and Scale, pull requests that get merge conflicts are rebuilt on their own, at most once a day, and never when someone has added their own commits
  • A migration that didn't open a pull request now says why in plain words, with Try again right next to it
  • Snooze a package upgrade for 30 days instead of dismissing it for good
  • Packages your Dependabot or Renovate settings ignore are left alone by the daily SDK scan too
  • The dashboard shows the engineer time Versyka has saved, when allowances reset, and a sample of the first scan's results while it runs
  • Choose the day your weekly summary arrives, and get a warning before the version-bump allowance runs out
  • Find repositories faster: filter covered, not covered or needing attention, and select or clear many at once
October 2026

Autopilot, CI status and package upgrades

  • Autopilot: every Monday the version bumps your covered repositories need open on their own, one tested pull request per repository
  • Your own CI shows next to each open Versyka pull request: passing, failing or running
  • Package upgrades: known vulnerabilities from OSV.dev grouped into the upgrades that fix them, with their own monthly version-bump allowance
  • Upgrades your code never imports are tagged and sorted last, and big version jumps get a warning before you start them
  • GitLab, plus Go, Java and Kotlin projects, including projects in subfolders of a larger repository
  • A Getting started checklist for new accounts, email settings per person, Add to Slack, and an option to commit as yourself for Vercel's Hobby plan
October 2026

Security upgrades

  • Every connected repository is checked daily against OSV.dev for known vulnerabilities in its npm and PyPI dependencies, using exact versions from the lockfile when there is one
  • Each finding shows the advisory, its severity and the first version that fixes it, in your dashboard
  • Fixes that need a major upgrade, the kind a version bump alone breaks, can be delivered as a tested Versyka pull request
  • Alerts close themselves once the vulnerable version is gone
October 2026

Model retirement calendar, MCP server and GitHub Action

  • Model retirement calendar: every retirement OpenAI, Anthropic, Google Gemini, Mistral and Cohere have announced, with replacements, sources and a calendar feed
  • Check a public GitHub repository for the retiring models it still calls, with every file and line, and add the dates to your calendar
  • MCP server: coding agents in Claude Code, Cursor and VS Code can check SDK versions, look up model retirements and read migration guides
  • GitHub Action: comments on pull requests that add a retiring model or an outdated SDK, and can fail the check. Your code stays on the runner
October 2026

SDK tracker, upgrade alerts, and twelve migration guides

  • Eight new migration guides, twelve in all: Anthropic, Google Gemini (Python and JavaScript), Pinecone, Firebase, Slack, Twilio and Auth0, each checked against the vendor's own docs
  • SDK tracker: a page for each of the 40 vendors Versyka watches, with latest versions, release notes and guides
  • Upgrade check: a migration-guide link on every result that has one, share links that carry the check in the URL, and samples for package.json, requirements.txt and pyproject.toml
  • Email alerts: ask the upgrade check to watch your API SDKs and get an email when a new major version ships or one is deprecated
  • Trust page: a one-page security fact sheet you can save as a PDF
  • Redesign: How it works follows along as you scroll, a monthly/yearly switch on Pricing, and guides with a contents list and copyable, highlighted code
October 2026

Self-serve plans and the customer dashboard

  • Subscribe online to Starter, Team or Scale, monthly or yearly, and connect GitHub from your welcome email
  • Customer dashboard: sign in with GitHub to see your plan, repositories covered, pull requests this month and every migration
  • Plan limits are applied automatically: covered repositories and a monthly pull request allowance, with nothing extra opened without your agreement
  • Billing portal for invoices, card changes and cancellation
October 2026

Python support, published pricing, and a simpler site

  • Python repositories: pip, uv, poetry and pipenv projects, verified with your pytest suite in an isolated virtual environment
  • The upgrade check and monitoring read requirements.txt, pyproject.toml and Pipfile, and look up versions on PyPI
  • 40 recognized API vendors across npm and PyPI
  • Published plans: Free, Team, Scale and API providers. Design partners stay free during the pilot
  • New Monitoring page and a lighter, faster website
October 2026

Dependency monitoring and repository settings

  • Daily scan of connected repositories flags API SDKs that are major versions behind or deprecated
  • Start a migration from an alert: Versyka fetches the vendor's release notes and migration guide automatically
  • New .versyka.yml settings: custom test and install commands, ignored paths, file limits, ignored packages
  • New Docs and Compare pages
October 2026

Free API upgrade check

  • Paste a package.json and see which API SDKs are major versions behind, with release-note links
  • Recognizes SDKs from 38 vendors, including Stripe, OpenAI, Anthropic, AWS, Twilio, Slack, Shopify, and Plaid
  • Pilot delivery: Versyka can now open the pull request directly on your repository
October 2026

Website, interactive demo, and design-partner program

  • Launched www.versyka.com with an interactive walkthrough of three benchmark migrations
  • Opened the design-partner program: free pilots on one real migration
  • Published our security model and privacy policy
October 2026

Migration engine and benchmark

  • Shared migration pipeline: rule → structural search → sandboxed edit → build and tests → pull request
  • Automatic retries: failing test output is fed back to the model, up to three attempts
  • Vendor package upgrades with lockfile updates when a change requires a newer version
  • Benchmark of realistic breaking changes modeled on payments, AI SDK, and cloud SDK migrations
  • Local CLI to run a migration on any repository without connecting it