From 9c05ad38319e2330d53c9e5d463083d8198b7925 Mon Sep 17 00:00:00 2001
From: Alphin Tom <alpha912@users.noreply.github.com>
Date: Thu, 26 Jun 2025 21:47:55 +0200
Subject: [PATCH] Bump to v0.5.0

---
 README.md             | 2 +-
 cli/package.json      | 2 +-
 cli/src/osf.ts        | 4 ++--
 cli/tests/cli.test.ts | 2 +-
 package-lock.json     | 6 +++---
 package.json          | 2 +-
 parser/package.json   | 2 +-
 spec/v0.5/osf-spec.md | 2 +-
 8 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 57f37ce..7b15191 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ OmniScript Format (OSF) unifies the strengths of:
 - **XLSX / YAML / JSON**: data tables, live formulas, charts
 
 `omniscript-core` provides the formal specification, parser, serializer, and
-reference CLI tooling for OSF.
+reference CLI tooling for OSF. **Current version: v0.5.0.**
 
 ---
 
diff --git a/cli/package.json b/cli/package.json
index f2ef122..05b34a3 100644
--- a/cli/package.json
+++ b/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@osf/cli",
-  "version": "0.1.0",
+  "version": "0.5.0",
   "description": "OmniScript Format (OSF) CLI tools",
   "main": "dist/osf.js",
   "bin": {
diff --git a/cli/src/osf.ts b/cli/src/osf.ts
index 37d453e..535a8a6 100644
--- a/cli/src/osf.ts
+++ b/cli/src/osf.ts
@@ -55,7 +55,7 @@ ajv.addFormat('date', /^\d{4}-\d{2}-\d{2}$/);
 const validateOsf = ajv.compile(schema);
 
 function showHelp(): void {
-  console.log('OmniScript Format (OSF) CLI v0.1.0');
+  console.log('OmniScript Format (OSF) CLI v0.5.0');
   console.log('Universal document DSL for LLMs and Git-native workflows\n');
   console.log('Usage: osf <command> [options]\n');
   console.log('Commands:');
@@ -75,7 +75,7 @@ function showHelp(): void {
 }
 
 function showVersion(): void {
-  console.log('0.1.0');
+  console.log('0.5.0');
 }
 
 function handleError(error: Error, context: string): never {
diff --git a/cli/tests/cli.test.ts b/cli/tests/cli.test.ts
index 27756c0..e7dfd92 100644
--- a/cli/tests/cli.test.ts
+++ b/cli/tests/cli.test.ts
@@ -87,7 +87,7 @@ describe('OSF CLI', () => {
     it('should show version when --version is passed', () => {
       const result = execSync(`node "${CLI_PATH}" --version`, { encoding: 'utf8' });
 
-      expect(result.trim()).toBe('0.1.0');
+      expect(result.trim()).toBe('0.5.0');
     });
 
     it('should show help when no arguments are passed', () => {
diff --git a/package-lock.json b/package-lock.json
index b3b51f3..c87c1cf 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "omniscript-core",
-  "version": "0.1.0",
+  "version": "0.5.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omniscript-core",
-      "version": "0.1.0",
+      "version": "0.5.0",
       "workspaces": [
         "parser",
         "cli"
@@ -19,7 +19,7 @@
     },
     "cli": {
       "name": "@osf/cli",
-      "version": "0.1.0",
+      "version": "0.5.0",
       "dependencies": {
         "ajv": "^8.12.0"
       },
diff --git a/package.json b/package.json
index 28f565e..c2826ea 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "omniscript-core",
-  "version": "0.1.0",
+  "version": "0.5.0",
   "description": "OmniScript Format (OSF) - universal document DSL for LLMs, agentic AI, and Git-native workflows",
   "private": true,
   "type": "commonjs",
diff --git a/parser/package.json b/parser/package.json
index 3d0109b..b933a6b 100644
--- a/parser/package.json
+++ b/parser/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@osf/parser",
-  "version": "0.1.0",
+  "version": "0.5.0",
   "description": "OmniScript Format (OSF) parser and serializer",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
diff --git a/spec/v0.5/osf-spec.md b/spec/v0.5/osf-spec.md
index 7b5b9ab..0f2c49b 100644
--- a/spec/v0.5/osf-spec.md
+++ b/spec/v0.5/osf-spec.md
@@ -8,7 +8,7 @@ purpose, design principles, syntax, and how it relates to existing standards
 like Markdown, LaTeX, JSON/YAML, and Office file formats. The goal is to make
 OSF accessible to developers, document engineers, and standards bodies, while
 ensuring it can be easily adopted in modern, AI-assisted and version-controlled
-authoring workflows.
+authoring workflows. **This draft corresponds to CLI/parser version 0.5.0.**
 
 ## Purpose and Scope