chore: migrate to changeset-based release flow on push to main

Author: DanielHreben

.github/workflows/release.yml

@@ -1,20 +1,23 @@
 name: Release
 
 on:
-  release:
-    types: [published]
+  push:
+    branches:
+      - main
 
 jobs:
   publish:
     runs-on: ubuntu-latest
     permissions:
-      contents: read
+      contents: write
       id-token: write
+      pull-requests: write
 
     steps:
       - name: Checkout code
         uses: actions/checkout@v6
         with:
+          fetch-depth: 0
           persist-credentials: false
 
       - name: Setup Node.js
@@ -29,16 +32,16 @@ jobs:
       - name: Run tests
         run: yarn test
 
-      - name: Build package
-        run: yarn build
-
       - name: Get Artifact Publish Token
         id: publish-token
         uses: atlassian-labs/artifact-publish-token@v1.0.1
         with:
           output-modes: npm
 
-      - name: Publish to Artifactory npm-public
-        run: yarn release
+      - name: Create Release Pull Request or Publish to Artifactory
+        uses: changesets/action@v1
+        with:
+          publish: yarn release
         env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_CONFIG_USERCONFIG: ${{ github.workspace }}/.npmrc-public

README.md

@@ -182,12 +182,14 @@ The library includes comprehensive tests covering:
 
 ## Releasing
 
-Releases are published to [Artifactory npm-public](https://packages.atlassian.com/api/npm/npm-public/) and forwarded to npmjs.org.
+Releases are published to [Artifactory npm-public](https://packages.atlassian.com/api/npm/npm-public/) and forwarded to npmjs.org using [Changesets](https://github.com/changesets/changesets).
 
-To publish a new release:
+### How to release
 
-1. Create a [GitHub Release](https://github.com/atlassian-labs/lexicographic-keys/releases/new) with a tag matching the new version (e.g. `1.2.0`).
-2. The [Release workflow](.github/workflows/release.yml) will automatically trigger, run tests, and publish the package using `changeset publish` via Artifactory.
+1. In your PR branch, run `yarn changeset` and follow the prompts to describe your changes and select a version bump type (patch/minor/major). This creates a changeset file — commit it with your PR.
+2. Merge your PR to `main`.
+3. The [Release workflow](.github/workflows/release.yml) will automatically open a **"Version Packages" PR** that bumps the version and updates the CHANGELOG.
+4. Review and merge the "Version Packages" PR — the workflow will then publish the new version to Artifactory automatically.
 
 > **Note:** Publishing uses [`atlassian-labs/artifact-publish-token`](https://github.com/atlassian-labs/artifact-publish-token) for authentication — no manual npm credentials are required.