MentorAgent
Menu
Italiano

Project

Support and versions

How MentorAgent is versioned, which versions still get fixes, how we handle a vulnerability and where to ask.

Versions

MentorAgent follows Semantic Versioning 2.0.0 from 1.0.0. The current version is 1.2.0.

Major
A breaking change to the public contract. Only here.
Minor
New features, compatible with the same major.
Patch
Fixes, nothing else.

Five packages, one version

They are released together, and each one requires the others at exactly the same version. Upgrade them together.

  • Novior.MentorAgent
  • Novior.MentorAgent.Abstractions
  • Novior.MentorAgent.Blazor
  • Novior.MentorAgent.Server
  • Novior.MentorAgent.Declarative

What the contract covers

  • the public C# API of the five packages;
  • the documented hub methods and events, SSE frames and HTTP endpoints;
  • the names of the tools the library gives the model;
  • the documented configuration keys.

What it doesn't

  • what the model says, or which tool it picks on a given turn;
  • the wording of the prompts the library builds;
  • log messages: the Novior.MentorAgent category prefix is stable, the text after it isn't.

Dependencies

A minor version may move the Microsoft packages to a newer compatible line. Your AI provider's packages stay yours to choose.

What changed

Every package contains the whole CHANGELOG.md, and the changelog in the documentation has every version.

Support window

MentorAgent runs on .NET 10. When a new version ships, the one before it doesn't stop at once: it keeps getting security fixes for a while.

VersionReceivesFor how long
The latest minortoday 1.2.x All fixes Until the next minor
The previous minortoday 1.1.x, until 27 January 2027; 1.0.x until 21 January 2027 Security fixes 3 months after the next minor ships
The previous majornone yet: 1.x is the first Security fixes 6 months after the next major ships
Older versions, previews and release candidates Nothing Upgrade to a supported version

Security

Found a vulnerability? Write privately to security@mentoragent.net, never in a public issue. The security page says what to include.

  1. We take it in charge

    Within 5 working days we confirm we've received it and start looking.

  2. We fix it

    In the supported versions, as soon as we can. It's best effort: no guaranteed time to a fix.

  3. We say so in public

    When the fix ships, a GitHub security advisory and the changelog say what was affected and which version to install.

The full policy, with how releases are built and checked, is in SECURITY.md on GitHub.

Where to ask

Search the issues and the discussions first: the answer may be there already.

We answer as best we can, with no guaranteed response time. The help section of the documentation covers the most common problems.