You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/versioning.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,22 +20,22 @@ Beginning with the 1.0.0 release, the following support policy will be applied f
20
20
21
21
1. New functionality and additive APIs will be introduced in MINOR releases within the current MAJOR version only
22
22
* New functionality will not be added to an earlier MAJOR version
23
-
2. Bugs will be fixed within either:
24
-
1. A new PATCH release against the latest MAJOR.MINOR version
25
-
2. A new MINOR release against the latest MAJOR version
26
-
3.Critical, blocking issues will be fixed against:
27
-
1.The latest MINOR version within _the current_ MAJOR version
28
-
2.The latest MINOR version within _one previous_ MAJOR version, until the latest MAJOR version has been published for 3 months
23
+
2. Bugs will be fixed in either:
24
+
1. A PATCH release against the latest MAJOR.MINOR version within _the latest_ MAJOR version only
25
+
2. A MINOR release against the latest MAJOR version within _the latest_ MAJOR version only
26
+
3.Bugs deemed by the maintainers to be critical or blocking will be fixed in both:
27
+
1.A PATCH release against _the latest_ MAJOR version, within its latest MAJOR.MINOR version
28
+
2.A PATCH release against _one previous_ MAJOR version, within its latest MAJOR.MINOR version
29
29
30
30
## Experimental APIs
31
31
32
32
MAJOR or MINOR version updates might introduce or alter APIs annotated as [`[Experimental]`](https://learn.microsoft.com/dotnet/api/system.diagnostics.codeanalysis.experimentalattribute). This attribute indicates that an API is experimental and it may change at any time--including within PATCH or MINOR version updates.
33
33
34
-
Experimental APIs require suppression of diagnostic codes specific to the MCP SDK APIs, using an `MCPEXP` prefix.
34
+
Experimental APIs require suppression of diagnostic codes specific to the MCP SDK APIs, using an `MCP` prefix.
35
35
36
36
## Breaking changes
37
37
38
-
Prior to the release of a stable 1.0.0 set of NuGet packages, the SDK remains in preview and breaking changes can be introduced without prior notice. All versions beginning with the stable 1.0.0 release will follow semantic versioning, and breaking changes will require increments to the MAJOR version.
38
+
Prior to the release of a stable 1.0.0 set of NuGet packages, the SDK remains in preview and breaking changes can be introduced without prior notice. Thereafter, the SDK follows Semantic Versioning and breaking changes against stable releases require increments to the MAJOR version.
39
39
40
40
If feasible, the SDK will support all versions of the MCP spec. However, if breaking changes to the spec make this infeasible, preference will be given to the most recent version of the MCP spec, and this would be considered a breaking change necessitating a new MAJOR version.
41
41
@@ -58,4 +58,4 @@ If APIs within the SDK become obsolete due to changes in the MCP spec or other e
58
58
2. Within a MAJOR version update, APIs may be marked as `[Obsolete]` to produce _build errors_ indicating the API is no longer functional and always throws exceptions. The build errors will provide guidance specific to the affected APIs.
59
59
3. Within a MAJOR version update, obsolete APIs may be removed. API removals are expected to be rare and avoided wherever possible, and `[Obsolete]` attributes will be applied ahead of the API removal.
60
60
61
-
Beginning with the 1.0.0 release, all obsoletions will use diagnostic codes specific to the MCP SDK APIs, using an `MCPOBS` prefix.
61
+
Beginning with the 1.0.0 release, all obsoletions will use diagnostic codes specific to the MCP SDK APIs, using an `MCP` prefix.
0 commit comments