Configure independent package publishing after alpha

- Remove linked packages configuration from Changesets
- Update documentation to reflect independent versioning strategy
- Update release process documentation with numbered steps

Author: polRk

.changeset/config.json

@@ -1,26 +1,11 @@
 {
 	"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
-	"changelog": "@changesets/cli/changelog",
+	"changelog": ["@changesets/changelog-github", { "repo": "ydb-platform/ydb-js-sdk" }],
 	"commit": false,
-	"fixed": [
-		[
-			"@ydbjs/abortable",
-			"@ydbjs/api",
-			"@ydbjs/auth",
-			"@ydbjs/core",
-			"@ydbjs/debug",
-			"@ydbjs/error",
-			"@ydbjs/query",
-			"@ydbjs/retry",
-			"@ydbjs/topic",
-			"@ydbjs/value"
-		]
-	],
+	"fixed": [],
 	"linked": [],
 	"access": "public",
 	"baseBranch": "main",
 	"updateInternalDependencies": "patch",
-	"ignore": [
-		"@ydbjs/examples-*"
-	]
+	"ignore": ["@ydbjs/examples-*"]
 }

AGENTS.md

@@ -480,7 +480,7 @@ Select affected packages, choose bump type (major/minor/patch), write user-facin
 **Important Rules:**
 
 - **DO NOT create CHANGELOG.md files manually** - Changesets automatically generates them from changeset files in `.changeset/` directory
-- **If you create or delete packages in `packages/` directory** - Update the `fixed` array in `.changeset/config.json` to include new packages or remove deleted ones (packages must be listed alphabetically)
+- **Do not add packages to the `fixed` array in `.changeset/config.json`** - we publish packages independently; only introduce fixed groups if we explicitly decide to lock versions again
 - Third-parties packages (`third-parties/`) are NOT included in `fixed` array - they version independently
 
 See `RELEASING.md` and `VERSIONING.md` for full release process

RELEASING.md

@@ -5,7 +5,7 @@ This document describes how we cut stable releases for all packages in this mono
 ## Versioning Strategy
 
 - Packages follow SemVer.
-- We release coordinated versions across `@ydbjs/*` where feasible.
+- Packages are versioned independently based on their own changesets.
 - Pre-releases use the `alpha` tag; stable uses `latest`.
 
 See VERSIONING.md for details.
@@ -20,38 +20,38 @@ See VERSIONING.md for details.
 
 ## Release Steps
 
-1) Ensure workspace builds and tests pass
+1. Ensure workspace builds and tests pass
 
 ```bash
 npm run build
 npm test:all
 ```
 
-2) Verify package entry points and exports with ATTW
+2. Verify package entry points and exports with ATTW
 
 ```bash
 npm run attw
 ```
 
-3) Bump versions and generate changelogs (Changesets)
+3. Bump versions and generate changelogs (Changesets)
 
 ```bash
 npx changeset version
 ```
 
-4) Publish to npm (stable)
+4. Publish to npm (stable)
 
 ```bash
 # Ensure you are authenticated: npm whoami
 NPM_CONFIG_PROVENANCE=true npx changeset publish
 ```
 
-5) Create GitHub Release
+5. Create GitHub Release
 
 - Tag matches monorepo state (e.g., v7.0.0)
 - Paste aggregated changelog highlights
 
-6) Announce breaking changes and migration notes
+6. Announce breaking changes and migration notes
 
 - Link MIGRATION.md sections in release notes
 

VERSIONING.md

@@ -6,16 +6,13 @@ We use Semantic Versioning for all `@ydbjs/*` packages.
 - MINOR: backwards-compatible features
 - PATCH: bug fixes and docs/typings improvements
 
-## Coordinated Releases
+## Independent Releases
 
-Where possible, packages share the same major/minor to reduce friction:
+Packages publish versions independently. Bump only the packages affected by a changeset and keep dependency ranges broad enough (typically `^major.minor.0`) for consumers to pick up compatible updates.
 
-- @ydbjs/core, @ydbjs/query, @ydbjs/value, @ydbjs/api, @ydbjs/error, @ydbjs/retry, @ydbjs/auth
-
-Internal APIs may evolve without public guarantees. Public APIs are documented in each package README and types.
+When a change requires updates in dependent packages, include changesets for each affected package so they release together, but do not force unrelated packages to bump.
 
 ## Pre-releases
 
 - Pre-releases use the `alpha` tag and semver pre-release identifiers (e.g., 7.0.0-alpha.33)
 - Stable releases use the `latest` tag
-