chore: release v1.0.0

README.md

@@ -26,7 +26,7 @@
 
 ## Description
 
-This is an implementation of an [MCP (Model Context Protocol) Server](https://modelcontextprotocol.io/quickstart/server) to allow different LLMs to query information from Sysdig Secure platform. **It is still in early development and not yet ready for production use.** New endpoints and functionalities will be added over time. The goal is to provide a simple and easy-to-use interface for querying information from Sysdig Secure platform using LLMs.
+This is an implementation of an [MCP (Model Context Protocol) Server](https://modelcontextprotocol.io/quickstart/server) to allow different LLMs to query information from Sysdig Secure platform. New tools and functionalities will be added over time following semantic versioning. The goal is to provide a simple and easy-to-use interface for querying information from Sysdig Secure platform using LLMs.
 
 ## Quickstart Guide
 

docs/RELEASING.md

@@ -9,12 +9,12 @@ The guidelines to follow would be:
 * CI/Refactorings/Internal changes -> No need to release new version.
 * Documentation changes -> No need to release new version.
 
-The current version of the project is not stable yet, so you need to follow the [Semver spec](https://semver.org/spec/v2.0.0.html), with the following guidelines:
+The project follows the [Semver spec](https://semver.org/spec/v2.0.0.html) with these guidelines:
 
-* Unless specified, do not attempt to stabilize the version. That is, do not try to update the version to >=1.0.0. Versions for now should be <1.0.0.
-* For minor changes, update only the Y in 0.X.Y. For example: 0.5.2 -> 0.5.3
-* For major/feature changes, update the X in 0.X.Y and set the Y to 0. For example: 0.5.2 -> 0.6.0
-* Before choosing if the changes are minor or major, check all the commits since the last tag.
+* **MAJOR (X.0.0)**: Breaking changes that are not backward compatible.
+* **MINOR (1.X.0)**: New functionality that is backward compatible.
+* **PATCH (1.0.X)**: Bug fixes that are backward compatible.
+* Before choosing the version bump, check all the commits since the last tag.
 
 After the commit is merged into the default branch the workflow will cross-compile the project and create a GitHub release of that version.
 Check the workflow file in case of doubt.

package.nix

@@ -1,7 +1,7 @@
 { buildGoModule, versionCheckHook }:
 buildGoModule (finalAttrs: {
   pname = "sysdig-mcp-server";
-  version = "0.6.1";
+  version = "1.0.0";
   src = ./.;
   # This hash is automatically re-calculated with `just rehash-package-nix`. This is automatically called as well by `just update`.
   vendorHash = "sha256-qMgFlDqzmtpxNOFCX9TsE4sjz0ZdvTJ5Q5IpA8lzG8g=";