From 336f1bf1c5ee43c220b0857b1b9e30945aa30f3e Mon Sep 17 00:00:00 2001
From: hamir-suspect <ahasanbasic@semaphore.io>
Date: Wed, 19 Nov 2025 11:12:39 +0100
Subject: [PATCH] release: bump version to v0.10.0

---
 README.md         | 7 +++++++
 package-lock.json | 4 ++--
 package.json      | 2 +-
 3 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 59cf372..2c47b78 100644
--- a/README.md
+++ b/README.md
@@ -34,3 +34,10 @@ The helper script `ci/build-ami.sh` also accepts the desired AMI ID as an option
 ```
 ./ci/build-ami.sh ubuntu-noble x86_64 ami-0123456789abcdef0
 ```
+
+## Release Process
+
+1. Start from an up-to-date `main` branch and run the usual checks (`npm test`, `npm run synth`) so the release is built on a clean state.
+2. Decide the next semantic version (for example `1.4.0`). Update `package.json` and `package-lock.json` by running `npm version --no-git-tag-version 1.4.0` (or edit both files manually if you prefer).
+3. Commit the version bump with a conventional message such as `chore(release): v1.4.0`.
+4. Create a matching annotated tag for the commit: `git tag -a v1.4.0 -m "Release v1.4.0"` and push both the branch and tag (`git push && git push origin v1.4.0`).
diff --git a/package-lock.json b/package-lock.json
index 707d6d5..49bac11 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "aws-semaphore-agent",
-  "version": "0.9.2",
+  "version": "0.10.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "aws-semaphore-agent",
-      "version": "0.9.2",
+      "version": "0.10.0",
       "dependencies": {
         "aws-cdk": "^2.164.1",
         "aws-cdk-lib": "^2.164.1",
diff --git a/package.json b/package.json
index b7110f1..197ec3c 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "aws-semaphore-agent",
-  "version": "0.9.2",
+  "version": "0.10.0",
   "bin": {
     "aws-semaphore-agent": "bin/aws-semaphore-agent.js"
   },