Release v1.0.7 (#19)

* ci: remove back-merge main to develop step

Remove the back-merge step that automatically synced changes from the main branch
to develop after a release. This eliminates the complex automatic conflict resolution
logic that tried to merge or force-resolve merge conflicts.

Simplifies the release workflow by avoiding potentially risky forced pushes to
develop and reduces complexity in the CI process.

* Merge back Release v1.0.6 (#17) (#18)

Release v1.0.6 (#17)

* chore: add .npmignore for cleaner npm package

* chore(package): update bin path and repository url syntax

Add the .claude directory to npm ignore to exclude development files.
Improve package.json metadata by correcting repository URL format to use
the git+ protocol and adjusting the CLI binary path to avoid a leading
relative path indicator, ensuring better compatibility with package tools.

* feat: implement automated release workflow

- Add master release workflow triggered from develop branch
- Integrate DXT packaging into main CI workflow
- Remove redundant release-dxt.yml workflow
- Update semantic-release config to disable npm publishing
- Add comprehensive release documentation with secrets guide
- Implement full GitFlow automation with back-merging

This allows contributors to release new versions with a single
workflow trigger from the develop branch. The process automatically:
1. Creates release branch with version updates
2. Opens PR to main
3. After merge: publishes to npm, creates GitHub release with DXT
4. Back-merges to develop

* feat: extend CI workflow to run on every push to main branches

- Rename workflow to ci-code-quality.yml
- Run on both pull requests AND pushes to main/develop
- Adjust PR-specific features to only run on PRs
- Update summaries to reflect branch vs PR context

This ensures code quality on all commits to protected branches.

* chore: add missing newline at end of config file

* fix: add workflow permissions and create CHANGELOG.md

- Add explicit permissions for contents and pull-requests in release workflow
- Create initial CHANGELOG.md for version tracking
- Fix 403 error when creating PRs from GitHub Actions

* feat: add pre-commit hooks for formatting and linting

- Configure husky to run pre-commit hooks
- Add lint-staged to run biome format and lint on staged files
- Ensures code quality before commits

* fix: update release workflow to handle GitHub Actions PR permissions

- Add support for GH_PAT as alternative to repository permissions
- Document required GitHub repository settings in RELEASING.md
- Add troubleshooting for 403 PR creation errors
- Fix lint-staged to only process supported file types

* fix: use GitHub CLI for PR creation to avoid permissions issue

- Replace github-script with gh CLI for more reliable PR creation
- Update documentation for fine-grained token permissions
- Add pull request write permission requirement

* chore: remove redundant source file ignores from ignore configs

Remove obsolete ignore rules for source and script directories in ignore
files to simplify project configuration and avoid conflicts with actual
publishing logic. This clarifies which files are included during packaging
and syncing, ensuring ignore files remain minimal and accurate.

* ci: use environment vars for signing certificates

Modify the CI workflow to pass signing certificates via environment variables instead of referencing secrets directly in the script.

This improves readability and consistency in handling sensitive data during the release process. Minor whitespace cleanups and formatting adjustments are also included for better maintainability.

* ci: update dxt command and remove signature verification

Replace signature verification step with cleaning the package in the CI workflow to streamline the process.

Remove redundant signature verification from the signing script to simplify signing and reduce failure points.

Delete the now-unused `.dxtignore` file that listed excluded files for the DXT package.

* refactor(logger): defer logger initialization and file setup

Improve startup performance and avoid module-level side effects by
lazily initializing loggers and deferring log file creation until the
first log event. Streamline logger initialization by centralizing file
logging setup and replacing synchronous early setup with on-demand
initialization. This enhances reliability and reduces unnecessary I/O
during import phases.
Also apply lazy logger instantiation to domain-related modules for
consistent behavior and safer side effect management.

* Deployment: Dockerfile and Smithery config (#6)

This PR adds files for deploying your MCP server on Smithery. After
deployment, users can use your server over streamable HTTP (hosted on
[Smithery](https://smithery.ai)) without needing to install any
dependencies.

### Changes
- Added **Dockerfile** to package your server for deployment.
- Added **Smithery Configuration** file to specify how to start your
server. See [documentation](https://smithery.ai/docs/build/deployments).
- Updated **README** to include installation command via Smithery. _Note
that the command only works after the server is deployed on Smithery._

### Server Details
- **Smithery ID**: `@AbdallahAHO/lokalise-mcp`
- **Server Homepage**:
[https://smithery.ai/server/@AbdallahAHO/lokalise-mcp](https://smithery.ai/server/@AbdallahAHO/lokalise-mcp?utm_campaign=pr&modal=claim)

### Action Items
- [X] **Build Passing**: We verified that the Docker builds and your
server starts up using an automated test.
- [ ] **Code Review**: Please review the changes to ensure the
configuration is accurate for your server.


*These files were automatically generated and tested by Smithery*

---------



* Update smithery.yaml

* feat(config): add MCP initialization config handling and prioritization (#12)

Introduce a handler extracting configuration from MCP client info during
initialization, enabling dynamic config setup based on client-provided
data.

Update configuration loader to prioritize MCP init config over
environment variables and other sources, ensuring runtime flexibility
and seamless integration with MCP clients.

Add comprehensive tests verifying MCP config precedence, boolean
parsing, nested config handling, and hostname extraction.

* ci: improve back-merge handling in release workflow

- Add proper error handling for merge conflicts
- Create PR automatically if conflicts occur
- Use proper git fetch and checkout commands
- Add GH_TOKEN for PR creation

* refactor: reorder exports to improve consistency

Adjust export statements in the transport module to maintain consistent ordering and grouping.

Also tidy up import order in several modules for improved readability and alphabetical consistency,
such as reordering imports in the contributors service and keys controller.

These changes focus on code style and maintainability without affecting runtime behavior.

* feat(usergroups): add complete user group management domain

Implement full user groups management including CLI commands, MCP tools,
and MCP resources to enable listing, retrieving, creating, updating, deleting,
and managing members and projects within user groups.

- Introduce domain exports and types with comprehensive Zod validation schemas
- Add controller layer handling input validation, error processing, and formatting
- Build service layer interfacing with Lokalise User Groups API for actual data operations
- Create detailed Markdown formatters for human-readable output of API responses
- Provide CLI commands for seamless command-line interaction and automation
- Register MCP tools exposing user group operations to the MCP server
- Register MCP resources enabling resource-based access to user groups via URI schemes

This modular setup establishes a robust user groups domain supporting team-based
permission management and integration with Lokalise platform workflows.

* feat(teamusers): add domain with CLI, service, controller, formatter, and MCP tools

Introduce a new domain for managing Lokalise team users including:
- CLI commands for listing, retrieving, updating, and deleting team users.
- Controller layer with validation and error handling.
- Service layer integrating Lokalise API for team user operations.
- Formatting of responses into readable markdown.
- MCP resource and tool registration supporting API and interactive usage.

Establishes a foundation for consistent and extensible team user management within the system.

* feat(queuedprocesses): add domain for monitoring async operations

Introduce a new queuedprocesses domain to support tracking and managing
background asynchronous processes within Lokalise projects. This includes:

- CLI commands for listing and retrieving queued process details with validation
- Controller layer for input validation, error handling, and response formatting
- Rich Markdown formatters presenting process status, details, and summaries
- Service layer encapsulating API communication with Lokalise SDK
- MCP resources enabling resource-based access to queued processes data
- Tools integration for MCP server with typed argument schemas and error handling
- Comprehensive TypeScript types and guards aligned with Lokalise SDK v9.0.0+

This domain provides a structured and user-friendly way to monitor various
async tasks such as file uploads, downloads, project imports/exports,
improving observability and operational control.

Closes #N/A

* refactor(prompts): expand and restructure MCP prompts with detailed schemas

Rebuilds the MCP prompt registration to provide comprehensive, structured
workflows for Lokalise operations using explicit, XML-like instructions
aligned with Claude 4 best practices.

- Replaces previous prompts with extensively detailed prompts covering
  project management, language localization, key management, tasks, workflows,
  team collaboration, compliance, and advanced workflows.
- Introduces strict Zod schemas defining argument validation and user-friendly
  parameter naming to improve usability and robustness.
- Enhances prompt guidance with stepwise instructions, context, and output
  formats to standardize responses and improve clarity.
- Enables parallel execution hints and comprehensive analysis steps for
  efficiency and thorough reporting.
- Adds new complex workflows including file upload review, team onboarding,
  automated review pipelines, process monitoring, and translation memory import.

This refactor significantly improves maintainability, clarity, and feature
coverage of prompts, setting a foundation for scalable, user-friendly
automation workflows within the MCP environment.

* feat(prompts): add workflows for post-upload and document extraction reviews

Introduce two new review workflows to improve translation task management:

- Add post-upload review workflow enabling creation of language-specific
  review tasks for files already uploaded to the platform with flexible
  assignee mapping and optional confirmation prior to task creation.
- Add document extraction review workflow that parses raw document content
  into translation keys, creates them in bulk, and sets up translation
  tasks with language-based assignee assignments.

Additionally, enhance key listing functionality by supporting filename-based
filtering to precisely select keys associated with specific files, improving
task scope accuracy.

These additions streamline review and translation setup processes for files
and document content, reducing manual overhead and enhancing assignment
flexibility.

* docs: update documentation

Provides a detailed, code-verified guide summarizing full MCP server
capabilities including 11 completed domains, 59 tools, 21 resources,
and 17 workflow prompts. Enhances project documentation with updated
architecture, usage examples, domain interfaces, and best practices to
support scalable development and onboarding. Updates metadata and
readme to reflect latest feature set and expanded domain coverage.

* chore(release): prepare release v1.0.4

* feat(bin): add CLI wrapper and update install scripts

Implement a new CLI wrapper script as the package's bin entry point to
ensure consistent and flexible server startup across global installs,
local setups, and npx usage.

Enhance the postinstall script to robustly set executable permissions on
both the new CLI wrapper and the existing dist entry point, improving
cross-platform reliability.

Add metadata fields and files array to package configuration for better
package management and publishing hygiene.

Expand README with detailed instructions for global and npx usage to
clarify recommended installation and running workflows for users.

* ci: improve back-merge strategy from main to develop

Update the back-merge process in CI to use the "theirs" merge strategy, automatically
resolving conflicts by favoring changes from the main branch during merges into develop.

Add a fallback force-resolution approach that resets develop and force-pushes a merge
result when automatic conflict resolution still fails, improving merge reliability
and reducing manual intervention.

This ensures smoother synchronization after releases and minimizes blocked workflows.

* refactor(tasks): enhance task formatting and error handling

Improve task list and detail formatting by adding comprehensive fields
such as progress, keys, words, and source language to provide richer task
snapshots. Introduce detailed language assignment formatting including user
and group listings with leverage info.

Refactor error handling in task tool functions to return formatted errors
instead of throwing, enhancing robustness and consistent error propagation.
These changes improve clarity and completeness of task reporting and
stabilize task tool error flows.

* ci: remove back-merge main to develop step

Remove the back-merge step that automatically synced changes from the main branch
to develop after a release. This eliminates the complex automatic conflict resolution
logic that tried to merge or force-resolve merge conflicts.

Simplifies the release workflow by avoiding potentially risky forced pushes to
develop and reduces complexity in the CI process.

* chore(release): prepare release v1.0.6

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: smithery-ai[bot] <194235850+smithery-ai[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* feat(projects): add initial languages support on project creation

Add support for specifying initial languages when creating a project.

If no explicit languages are provided, default to including the base
language as an initial language when it differs from English.

Update request validation schema to accept an optional languages array,
improving flexibility and correctness in project language initialization.

* refactor(keys): unify key name display logic into helper function

Extract key name formatting into a single helper to ensure consistent
rendering across different platforms and key listing functions.

This enhances maintainability and avoids duplication by centralizing the
logic that handles varied key name formats or missing values.

* test(tasks): add fixtures and extensive formatter tests

Add comprehensive test fixtures representing various task scenarios including
lists, pagination, creation, retrieval, and deletion states. Introduce detailed
snapshot tests for task formatting to cover rich metadata, language assignments,
due date handling, edge cases (nulls, invalid dates, long content), and markdown
escaping.

Implement a helper for paginated results and mock current date/time for stable,
repeatable test snapshots. Fix language code handling to safely support null/undefined
values in formatter output.

This improves test coverage and reliability for task domain formatting logic,
facilitating better validation of output formatting and edge case handling.

* test(projects): add fixtures and comprehensive formatter tests

Introduce detailed test fixtures for project domain with realistic sample data
covering list retrieval, pagination, creation, update, deletion, and emptying states.

Add extensive snapshot-based tests for project formatter functions to verify correct
handling of various scenarios including null/undefined fields, zero statistics,
invalid dates, special characters, and very long names.

Ensure stable and consistent test output by mocking Date to a fixed timestamp.

These enhancements improve test coverage, reliability, and maintainability of
project-related formatting and data handling logic.

* test(keys): add fixtures and snapshot tests for keys formatting

Introduce comprehensive test fixtures simulating various keys API responses
and cursor pagination scenarios to enable robust testing of keys formatting.
Add detailed snapshot tests covering key listing, retrieval, creation, update,
deletion, bulk operations, and edge cases to ensure formatting consistency and
handle nulls, special characters, long key names, comments, and screenshots.

* chore(bin): update imports to use node: protocol and improve typings

Update native module imports to use the explicit `node:` protocol for clarity
and compliance with current Node.js standards.

chore(scripts): silence unused error variable warning

Rename unused error variable to underscore-prefixed to avoid linter warnings
while maintaining silent failure behavior on chmod errors.

chore(tsconfig): exclude fixtures and test files from the build

Exclude test and fixture files from TypeScript compilation to streamline
type checking and improve build performance.

* chore(release): prepare release v1.0.7

---------

Co-authored-by: Abdallah Othman <abdallah.othman@lokalise.com>
Co-authored-by: Abdallah Othman <Abdallah.ali.hassan@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: smithery-ai[bot] <194235850+smithery-ai[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: 3 people

.github/workflows/ci-semantic-release.yml

@@ -179,50 +179,6 @@ jobs:
                       ### 📋 What's Changed
                       See the full changelog below for all changes in this release.
 
-            # Step 11: Back-merge to develop
-            - name: Back-merge to develop
-              env:
-                  GH_TOKEN: ${{ secrets.GH_PAT || secrets.GITHUB_TOKEN }}
-              run: |
-                  # Fetch latest branches
-                  git fetch origin develop:refs/remotes/origin/develop
-                  git fetch origin main:refs/remotes/origin/main
-
-                  # Checkout develop
-                  git checkout -B develop origin/develop
-
-                  # Try to merge main with strategy to automatically resolve conflicts
-                  # Using -X theirs to always take changes from main when conflicts occur
-                  echo "🔄 Attempting to merge main into develop..."
-                  
-                  if git merge origin/main -X theirs -m "chore: back-merge main to develop after v${{ steps.get-version.outputs.version }} release" --no-edit; then
-                      echo "✅ Merge successful (conflicts auto-resolved using main's version)"
-                      # Push to develop
-                      git push origin develop
-                      echo "✅ Successfully pushed merged changes to develop"
-                  else
-                      # This should rarely happen with -X theirs, but handle it just in case
-                      echo "⚠️ Unexpected merge failure even with auto-resolution. Attempting force resolution..."
-                      
-                      # Reset to develop and try a different approach
-                      git reset --hard origin/develop
-                      
-                      # Create a temporary branch from main
-                      git checkout -B temp-main origin/main
-                      
-                      # Merge develop into this branch (reverse merge) and take all from main
-                      git merge origin/develop --strategy=ours -m "chore: back-merge main to develop after v${{ steps.get-version.outputs.version }} release (force resolved)"
-                      
-                      # Now force push this as the new develop
-                      git branch -f develop HEAD
-                      git checkout develop
-                      
-                      # Push the resolved develop branch
-                      git push origin develop --force-with-lease
-                      
-                      echo "✅ Force-resolved conflicts by taking all changes from main"
-                  fi
-
             # Step 12: Summary
             - name: Release Summary
               run: |

CHANGELOG.md

@@ -1,3 +1,30 @@
+## [1.0.7] - 2025-08-14
+
+### Added
+- **Initial Languages Support on Project Creation**: Enhanced project creation to support specifying initial languages when creating a project, with automatic base language inclusion when it differs from English
+- **Comprehensive Test Coverage**: Added extensive test fixtures and snapshot tests for keys, projects, and tasks domains to improve reliability and maintainability
+- **Enhanced Key Name Display Logic**: Unified key name display logic into helper function for consistent formatting across the application
+
+### Changed
+- **Node.js Import Standards**: Updated native module imports to use explicit `node:` protocol for clarity and compliance with current Node.js standards
+- **TypeScript Build Optimization**: Excluded test and fixture files from TypeScript compilation to streamline build process
+- **Improved Error Handling**: Enhanced error handling in scripts with better variable naming to avoid linter warnings
+
+### Fixed
+- **Test Stability**: Implemented stable and repeatable test snapshots by mocking Date to fixed timestamps
+- **Language Code Handling**: Fixed language code handling in task formatters to safely support null/undefined values
+- **Test Coverage**: Added comprehensive test coverage for edge cases including nulls, invalid dates, long content, and markdown escaping
+
+### Developer Experience
+- **Test Infrastructure**: Added 2,130+ lines of test code including fixtures and snapshots
+- **Formatter Testing**: Comprehensive snapshot tests for keys, projects, and tasks formatting
+- **Edge Case Coverage**: Robust testing for special characters, long names, comments, and screenshots
+
+## [1.0.6] - 2025-08-14
+### Changed
+- Fixed the error handling in the MCP server for tasks domain and return formatErrorForMcpTool for all tools
+- Improved the tasks tool response formatting to include more information about the task
+
 ## [1.0.5] - 2025-08-12
 
 ### Added

bin/lokalise-mcp.js

@@ -7,9 +7,9 @@
  * globally, locally, or via npx.
  */
 
-import { spawn } from "child_process";
-import { fileURLToPath } from "url";
-import { dirname, join } from "path";
+import { spawn } from "node:child_process";
+import { fileURLToPath } from "node:url";
+import { dirname, join } from "node:path";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);

manifest.json

@@ -2,7 +2,7 @@
 	"dxt_version": "0.1",
 	"name": "lokalise-mcp",
 	"display_name": "Lokalise MCP",
-	"version": "1.0.5",
+	"version": "1.0.7",
 	"description": "Unofficial Lokalise integration for AI assistants - manage projects, keys, languages, tasks, translations, teams, and workflows through natural language with 59 intelligent tools across 11 domains.",
 	"long_description": "# Lokalise MCP Server\n\n> **Disclaimer**: This is an independent project and not affiliated with Lokalise Inc. It uses the publicly available Lokalise Node.js SDK to provide MCP integration.\n\n## Transform Your Localization Workflow with Conversational AI\n\n**Stop clicking, start commanding.** With 59 intelligent tools across 9 domains, this MCP server transforms Lokalise from a complex UI into your personal localization assistant. Simply describe what you need in natural language, and watch as your AI orchestrates sophisticated API workflows in seconds.\n\nInstead of clicking through multiple screens, just chat with your AI assistant:\n- *\"Show me all projects with less than 80% translation progress\"*\n- *\"Create a new mobile app project with German, French, and Spanish support\"*\n- *\"Find all untranslated keys in the iOS app and assign them to the German team\"*\n- *\"Archive all keys tagged 'v1_deprecated' across all projects\"*\n\n### 59 Production-Ready Tools Across 9 Domains\n\n**Contributors (5 tools)** - Team collaboration and permission management\n**Keys (5 tools)** - Intelligent key management with bulk operations and smart filtering\n**Glossary (5 tools)** - Terminology consistency and brand voice enforcement\n**Project (5 tools)** - Comprehensive project management capabilities\n**Tasks (5 tools)** - Workflow automation and deadline management\n**Group (4 tools)** - Comprehensive group management capabilities\n**Projects (4 tools)** - Complete project lifecycle management from creation to archival\n**Translations (4 tools)** - Direct translation management with review workflows\n\n### Real-World Workflows That Save Hours\n\n**For Localization Managers:**\n- *Morning standup in 10 seconds*: \"Give me the health check for all active projects. Who's behind schedule?\"\n- *Instant team scaling*: \"Add marie@company.com as a French reviewer to all e-commerce projects\"\n- *Proactive monitoring*: \"Alert me when any project drops below 70% completion\"\n\n**For Developers:**\n- *Zero-friction deployment*: \"Sync the feature/new-login branch to Lokalise and create tasks for Spanish and German\"\n- *Instant validation*: \"Check if all keys in the Android app have iOS equivalents\"\n- *Automated QA*: \"Find all keys with unbalanced brackets and create a cleanup task\"\n\n**For Marketing Teams:**\n- *Campaign launch in one command*: \"Create a project from this Google Doc, translate to our tier-1 markets, use informal tone\"\n- *Brand consistency*: \"Add 'QuantumLeap' to the glossary as non-translatable across all projects\"\n- *Content updates*: \"Update all homepage headlines with the new tagline across all languages\"\n\n**Traditional UI Workflow:**\n- Navigate through multiple screens\n- Click through complex forms\n- Context switch between tools\n- Time: 10-15 minutes per task\n\n**Conversational MCP Workflow:**\n- Express intent in natural language\n- AI orchestrates API calls\n- Results delivered instantly\n- Time: 10-30 seconds per task\n\n\n### Get Started in 30 Seconds\n\n1. Install the MCP server\n2. Add your Lokalise API token\n3. Start commanding your localization workflow\n",
 	"author": {

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "lokalise-mcp",
-	"version": "1.0.5",
+	"version": "1.0.7",
 	"description": "The Lokalise MCP Server brings Lokalise's localization power to Claude and AI assistants—manage projects, keys, and translations by chat.",
 	"main": "dist/index.js",
 	"types": "dist/index.d.ts",
@@ -42,8 +42,8 @@
 		"release:sign": "node scripts/sign-dxt.js",
 		"scaffold:domain": "node scripts/scaffold-domain.js",
 		"scaffold:domain:cli": "node scripts/scaffold-domain-cli.js",
-		"test": "NODE_OPTIONS='--experimental-vm-modules' jest",
-		"test:coverage": "NODE_OPTIONS='--experimental-vm-modules' jest --coverage",
+		"test": "TZ=UTC NODE_OPTIONS='--experimental-vm-modules' jest",
+		"test:coverage": "TZ=UTC NODE_OPTIONS='--experimental-vm-modules' jest --coverage",
 		"update:deps": "npx npm-check-updates -u && npm install --legacy-peer-deps",
 		"validate:manifest": "node scripts/generate-manifest.js --validate"
 	},

release/checksums.sha256

@@ -1 +1 @@
-c6c87d16f754fcd0be625a87228a7228d09ea16792676b27679a1b5687b23e30  lokalise-mcp-1.0.5.dxt
+0a212fa43fdd232b8402d96c3bfcf4ff809380a0a55346be379c3eb78fa6e507  lokalise-mcp-1.0.7.dxt

release/lokalise-mcp-1.0.5.dxt

@@ -1,19 +1,19 @@
 {
-	"version": "1.0.5",
-	"date": "2025-08-12T09:17:25.228Z",
+	"version": "1.0.7",
+	"date": "2025-08-14T09:44:53.829Z",
 	"assets": [
 		{
-			"filename": "lokalise-mcp-1.0.5.dxt",
-			"sha256": "c6c87d16f754fcd0be625a87228a7228d09ea16792676b27679a1b5687b23e30"
+			"filename": "lokalise-mcp-1.0.7.dxt",
+			"sha256": "0a212fa43fdd232b8402d96c3bfcf4ff809380a0a55346be379c3eb78fa6e507"
 		}
 	],
 	"npm": {
 		"package": "lokalise-mcp",
-		"version": "1.0.5",
+		"version": "1.0.7",
 		"registry": "https://registry.npmjs.org/"
 	},
 	"github": {
 		"repository": "AbdallahAHO/lokalise-mcp",
-		"tag": "v1.0.5"
+		"tag": "v1.0.7"
 	}
 }

release/lokalise-mcp-1.0.4.dxt release/lokalise-mcp-1.0.7.dxtrelease/lokalise-mcp-1.0.4.dxt renamed to release/lokalise-mcp-1.0.7.dxt

@@ -15,7 +15,7 @@ try {
 	if (fs.existsSync(binScript)) {
 		try {
 			fs.chmodSync(binScript, 0o755);
-		} catch (err) {
+		} catch (_err) {
 			// Silently fail if chmod is not available (Windows, some containers)
 		}
 	}