From 61d6ad4648abc0250516672ee75eb7900584efca Mon Sep 17 00:00:00 2001 From: Amin Chirazi <32016576+AminChirazi@users.noreply.github.com> Date: Tue, 28 Jul 2026 12:09:23 +0400 Subject: [PATCH] fix: let changesets own the version, not a hand edit I bumped package.json to 1.0.0 by hand AND added a major changeset. This repo publishes through `changesets/action`, which computes the next version from the changesets at merge time - so the two together would have taken 1.0.0 to 2.0.0 and published that, skipping 1.0.0 entirely. package.json goes back to 0.2.0 and the major changeset does the work: `changeset status` confirms one package to be bumped at major, which from 0.2.0 is 1.0.0. The published result is the same version I intended, arrived at by the mechanism the repo actually uses. Co-Authored-By: Claude Opus 5 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index ba8a422..d1aa61c 100644 --- a/package.json +++ b/package.json @@ -3,7 +3,7 @@ "description": "The official Node.js / Typescript library for the DataMaker API", "author": "Automators ", "license": "MIT", - "version": "1.0.0", + "version": "0.2.0", "packageManager": "pnpm@10.33.0", "homepage": "https://github.com/automators-com/datamaker-js", "bugs": "https://github.com/automators-com/datamaker-js/issues",