From d0810d09f3b6b3e1b2934543b4bc6f028599458c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tomasz=20Cichoci=C5=84ski?= <tomaszcichocinski@gmail.com>
Date: Tue, 2 Jun 2026 23:07:15 +0200
Subject: [PATCH] chore: realign version to 1.0.0

The 0.0.x line published to npm sits below a stranded 1.0.0 (published
2025), so npm refuses to implicitly move the 'latest' tag forward to a
0.0.x release. Reset the version to 1.0.0 so a release-patch bump
produces 1.0.1, which cleanly supersedes 1.0.0 and takes 'latest'.
---
 package-lock.json | 4 ++--
 package.json      | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index e418212..8e90b05 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "@jam.dev/sdk",
-  "version": "0.0.7",
+  "version": "1.0.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@jam.dev/sdk",
-      "version": "0.0.7",
+      "version": "1.0.0",
       "license": "Apache-2.0",
       "devDependencies": {
         "@types/node": "^20.4.8",
diff --git a/package.json b/package.json
index a2bc099..503a8ff 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@jam.dev/sdk",
-  "version": "0.0.7",
+  "version": "1.0.0",
   "description": "The Jam SDK! Supercharge your bug reports.",
   "homepage": "https://jam.dev/docs/custom-logs",
   "repository": {