feat: migrate Changesets functionality from main to develop branch

- Add Changesets configuration for semantic versioning and automated releases
- Update all package versions to 1.16.1 (aligned with develop branch)
- Create initial CHANGELOG.md files for all ATS packages
- Update GitHub Actions workflow for changesets automation with Node.js 22.x
- Configure fixed versioning for ATS packages, independent versioning for mass-payout
- Add all changeset management scripts to root package.json
- Update documentation for new version management workflow

This establishes the foundation for automated version management using Changesets
while maintaining compatibility with the develop branch codebase.

Migrated from origin/feat/changesets (commit 93ce464) with conflict resolution
and version alignment to preserve develop branch state.

Signed-off-by: Miguel_LZPF <miguel.carpena@io.builders>

Author: MiguelLZPF

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,17 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [
+    [
+      "@hashgraph/asset-tokenization-contracts",
+      "@hashgraph/asset-tokenization-sdk",
+      "@hashgraph/asset-tokenization-dapp"
+    ]
+  ],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.github/workflows/all.publish.yml

@@ -1,19 +1,32 @@
 name: Publishing
 
-
 on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types:
+      - closed
+    branches:
+      - main
   release:
-    types: [published]
-
+    types:
+      - published
 
 permissions:
-  contents: read
+  contents: write
+  pull-requests: write
+  id-token: write
 
 jobs:
-  publish:
-    name: Publish NPM Packages
-    runs-on: ubuntu-latest
+  release:
+    name: Release with Changesets
+    runs-on: token-studio-linux-large
+    # Only run for direct pushes to main OR merged PRs to main
+    if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.pull_request.merged == true)
     env:
+      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
       NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
     steps:
@@ -24,25 +37,57 @@ jobs:
 
       - name: Checkout repository
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          fetch-depth: 0
 
       - name: Setup NodeJS Environment
         uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
-          node-version: 20.x
+          node-version: 22.x
+          registry-url: https://registry.npmjs.org
 
       - name: Install dependencies
         run: npm ci
 
-      # --- ATS publishing ---
-      - name: Publish ats/contracts
-        if: contains(github.ref_name, 'ats')
-        run: npm run ats:contracts:publish
+      - name: Build packages
+        run: npm run ats:build
+
+      - name: Create Release Pull Request or Publish
+        uses: changesets/action@v1
+        with:
+          version: npm run changeset:version
+          publish: npm run changeset:publish
+          title: 'chore: release packages'
+          commit: 'chore: release packages'
+
+  # Legacy manual release workflow (emergency fallback only)
+  manual-publish:
+    name: Manual Publish (Emergency)
+    runs-on: token-studio-linux-large
+    if: github.event_name == 'release' && github.event.action == 'published'
+    env:
+      NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+    steps:
+      - name: Harden Runner
+        uses: step-security/harden-runner@0634a2670c59f64b4a01f0f96f84700a4088b9f0 # v2.12.0
+        with:
+          egress-policy: audit
+
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+      - name: Setup NodeJS Environment
+        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+        with:
+          node-version: 22.x
+          registry-url: https://registry.npmjs.org
+
+      - name: Install dependencies
+        run: npm ci
 
-      - name: Publish ats/sdk
-        if: contains(github.ref_name, 'ats')
-        run: npm run ats:sdk:publish
+      - name: Build packages
+        run: npm run ats:build
 
-      # --- Mass Payout publishing ---
-      - name: Publish mass-payout
-        if: contains(github.ref_name, 'mp')
-        run: npm run mass-payout:publish
+      - name: Publish packages directly
+        run: npm run ats:publish

README.md

@@ -121,8 +121,11 @@ npm run ats:test:ci            # Run CI tests
 npm run ats:start              # Build contracts/SDK and start web dev server
 npm run ats:web:dev           # Start web dev server only
 
-# Publishing (for maintainers)
-npm run ats:publish           # Publish contracts and SDK to npm
+# Version management and publishing
+npm run changeset             # Create changeset for new changes
+npm run changeset:version     # Update versions based on changesets
+npm run changeset:publish     # Publish updated packages to npm
+npm run release              # Build all components and publish
 ```
 
 ### Mass Payout (Placeholder)
@@ -338,13 +341,70 @@ npm run clean:deps
 npm ci
 ```
 
+## Version Management
+
+The project uses **Changesets** for semantic versioning and automated release management.
+
+### Version Strategy
+
+- **ATS packages** (contracts, SDK, web): Use **fixed versioning** - all packages share the same version and are released together
+- **Mass-payout packages**: Use **independent versioning** - versioned separately from ATS
+
+### Changeset Workflow
+
+For developers making changes:
+
+1. **Make your changes** to any package
+2. **Create a changeset** describing your changes:
+
+   ```bash
+   npm run changeset
+   ```
+
+   This creates a changeset file describing what changed and the type of change (patch/minor/major)
+
+3. **Commit both** your code changes and the changeset file:
+   ```bash
+   git add .
+   git commit -m "feat: add new functionality"
+   ```
+
+For maintainers releasing versions:
+
+1. **Review pending changes**:
+
+   ```bash
+   npm run changeset:status
+   ```
+
+2. **Update versions** (consumes changesets and updates package versions):
+
+   ```bash
+   npm run changeset:version
+   git commit -m "chore: release version x.x.x"
+   ```
+
+3. **Build and publish** packages:
+   ```bash
+   npm run release
+   ```
+
+### Automated Releases
+
+The GitHub Actions workflow automatically:
+
+- Creates "Release PRs" when changesets are pending
+- Publishes packages when Release PRs are merged
+- Generates changelogs from changeset descriptions
+- Creates GitHub releases with proper release notes
+
 ## Continuous Integration
 
 The project uses separate GitHub Actions workflows for different components:
 
-- **ATS Tests** (`.github/workflows/test-ats.yml`): Runs when ATS-related files change
-- **Mass Payout Tests** (`.github/workflows/test-mp.yml`): Runs when Mass Payout files change
-- **Publishing** (`.github/workflows/publish.yml`): Handles publishing to npm with conditional logic based on release tags
+- **ATS Tests** (`.github/workflows/ats.test.yml`): Runs when ATS-related files change
+- **Mass Payout Tests** (`.github/workflows/mp.test.yml`): Runs when Mass Payout files change
+- **Publishing** (`.github/workflows/all.publish.yml`): Automated releases using Changesets
 
 Tests are automatically triggered only when relevant files are modified, improving CI efficiency.
 

apps/ats/web/CHANGELOG.md

@@ -0,0 +1,11 @@
+# @hashgraph/asset-tokenization-dapp
+
+## 1.16.1
+
+### Patch Changes
+
+- Initial setup of Changesets for version management
+
+  This changeset establishes the baseline for the new version management system using Changesets. All ATS packages are now aligned to version 1.16.1 and will be managed together using fixed versioning.
+
+  Mass-payout packages will continue to be versioned independently.

docs/dev-monorepo-migration.md

@@ -66,6 +66,14 @@ The Asset Tokenization Studio has been restructured into a proper npm workspaces
 | Test web       | `cd web && npm test`       | `npm run ats:web:test`       |
 | Test all       | Manual in each directory   | `npm run ats:test`           |
 
+### Version Management Commands
+
+| Task                    | Old Command                | New Command                                       |
+| ----------------------- | -------------------------- | ------------------------------------------------- |
+| Update package versions | `./changeVersion.sh 1.0.0` | `npm run changeset` → `npm run changeset:version` |
+| Publish packages        | Manual npm publish         | `npm run changeset:publish`                       |
+| Build and publish       | Multiple manual steps      | `npm run release`                                 |
+
 ### Environment Setup
 
 **Before:**
@@ -122,6 +130,8 @@ If you have custom scripts or CI/CD configurations, update them to use the new w
 3. **Better CI/CD**: Path-based test triggers and conditional publishing
 4. **Scalability**: Ready for additional packages (e.g., mass-payout)
 5. **Consistent Tooling**: Centralized linting and formatting configurations ensure code quality consistency across all packages
+6. **Modern Version Management**: Changesets provide automated semantic versioning, changelog generation, and release management
+7. **Enterprise-Grade Releases**: Automated release workflows with proper audit trails and documentation
 
 ## Troubleshooting
 
@@ -142,6 +152,19 @@ npm run ats:web:build
 **Issue**: Environment variables not working
 **Solution**: Check that your `.env` file is in `apps/ats/web/.env`
 
+**Issue**: Version management with old script
+**Solution**: The `changeVersion.sh` script has been replaced by Changesets:
+
+```bash
+# Old way (deprecated)
+./changeVersion.sh 1.0.0
+
+# New way
+npm run changeset              # Create changeset for changes
+npm run changeset:version      # Update package versions
+npm run release               # Build and publish
+```
+
 ### Getting Help
 
 If you encounter issues during migration: