This is a hotfix release that addresses a critical bug affecting Jira write operations and improves the consistency of read-only mode handling across all tools.
🐞 Fixed
- Jira Write Operations in Read-Only Mode: Fixed an
AttributeError: 'JiraConfig' object has no attribute 'read_only'
that occurred when attempting to use Jira write tools. This issue (reported in #434) was caused by recent authentication refactoring. Theread_only
check now correctly uses the global application context. - Standardized Read-Only Checks: All Jira and Confluence write-enabled tools now use a common
@check_write_access
decorator to manage read-only mode restrictions. This ensures consistent behavior and makes the codebase cleaner. (PR #438)
⚙️ Internal
- Introduced a
@check_write_access
decorator insrc/mcp_atlassian/utils/decorators.py
for centralized read-only mode logic. - Refactored Jira and Confluence server tool definitions to utilize the new decorator, removing repetitive manual checks.
- Added unit tests for the new decorator.
This fix ensures that the READ_ONLY_MODE
environment variable correctly restricts write operations for both Jira and Confluence tools as intended.
Full Changelog: v0.11.0...v0.11.1