Release Candidate v5.19.8 (#426)

Author: milosmns

.agent/rules/code-style.md

@@ -8,3 +8,9 @@ globs: *ts,*.js,*.jsx,*.tsx
 #### JavaScript/TypeScript
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
+
+#### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it

.agent/rules/tooling.md

@@ -20,6 +20,7 @@ globs: *.ts,*.tsx,*.js,*.jsx
 ### Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

.claude/CLAUDE.md

@@ -8,6 +8,12 @@
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
 
+### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it
+
 ## Environment Management
 
 - ALWAYS use both `bun` and `npm` for dependency management
@@ -23,6 +29,7 @@ In JavaScript and TypeScript, use types as much as possible: strict mode will be
 ## Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

.cursor/rules/style.mdc

@@ -8,3 +8,9 @@ alwaysApply: false
 #### JavaScript/TypeScript
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
+
+#### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it

.cursor/rules/tooling.mdc

@@ -20,6 +20,7 @@ alwaysApply: true
 ### Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

.windsurf/rules/rules.md

@@ -4,6 +4,12 @@
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
 
+### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it
+
 ---
 
 ## MANDATORY PROJECT RULES
@@ -23,6 +29,7 @@ In JavaScript and TypeScript, use types as much as possible: strict mode will be
 ### Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

AGENTS.md

@@ -4,6 +4,12 @@
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
 
+### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it
+
 ---
 
 ## MANDATORY PROJECT RULES
@@ -23,6 +29,7 @@ In JavaScript and TypeScript, use types as much as possible: strict mode will be
 ### Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

GEMINI.md

@@ -6,6 +6,12 @@
 
 In JavaScript and TypeScript, use types as much as possible: strict mode will be turned on! If in doubt, follow Java standard formatting. Finally, we also always want trailing commas in multi-line code blocks.
 
+### Comments
+
+- For new code, avoid comments unless the logic is genuinely complex or the block is long
+- When editing existing code, prefer updating comments over deleting them
+- Comments should start with a lowercase letter, except in documentation or where grammar requires it
+
 ## Environment Management
 
 - ALWAYS use both `bun` and `npm` for dependency management
@@ -21,6 +27,7 @@ In JavaScript and TypeScript, use types as much as possible: strict mode will be
 ## Project Structure
 
 - Version is managed through the `version` property of the `package.json` file
+- For version bumps, run `bun run bump {major|minor|patch}`; major and minor bumps reset lower version segments, and the script updates both project config and lock files
 - You can see the CI/CD pipeline in `.github/workflows` directory
 - It's best to base API implementation on API docs. If you don't have any, ask for them
 

package-lock.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-web",
   "private": true,
-  "version": "5.19.7",
+  "version": "5.19.8",
   "type": "module",
   "scripts": {
     "clean": "rm -rf dist .vite node_modules/.vite",
@@ -14,7 +14,8 @@
     "lint:css": "stylelint \"**/*.css\" --ignore-path .gitignore",
     "lint:i18n": "bun run i18n:keys && bun run i18n:check",
     "i18n:keys": "bun scripts/generate-translation-keys.ts",
-    "i18n:check": "bun scripts/check-translation-usage.ts"
+    "i18n:check": "bun scripts/check-translation-usage.ts",
+    "bump": "bun scripts/bump-version.ts"
   },
   "dependencies": {
     "@radix-ui/react-accordion": "^1.2.14",
@@ -65,7 +66,7 @@
     "postcss-nesting": "^14.0.0",
     "postcss-theme-ui": "^0.10.0",
     "shadcn": "^4.11.0",
-    "stylelint": "17.13.0",
+    "stylelint": "17.14.0",
     "stylelint-config-standard": "^40.0.0",
     "stylelint-config-tailwindcss": "^1.0.1",
     "tw-animate-css": "^1.4.0",