Release v1.0.3 - #13
Merged
Merged
Conversation
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.
- 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
- 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.
feat: Automated Release Workflow
- 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
- Configure husky to run pre-commit hooks - Add lint-staged to run biome format and lint on staged files - Ensures code quality before commits
- 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
- Replace github-script with gh CLI for more reliable PR creation - Update documentation for fine-grained token permissions - Add pull request write permission requirement
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.
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.
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.
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.
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* --------- Co-authored-by: smithery-ai[bot] <194235850+smithery-ai[bot]@users.noreply.github.com>
…on (#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.
AbdallahAHO
force-pushed
the
release/v1.0.3
branch
from
August 11, 2025 07:56
184db09 to
ca33259
Compare
AbdallahAHO
force-pushed
the
release/v1.0.3
branch
from
August 11, 2025 07:58
ca33259 to
e55e0dc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Release v1.0.3
Release Type: patch
Pre-release Checklist
Post-merge Actions
After merging this PR, the following will happen automatically:
v1.0.3This PR was automatically created by the release workflow.