Repository navigation
Releases
v2.0.0
2.0.0 (2026-11-02)
Migration from 1.x
This is a major release because setup now requires Node.js 22 or later, explicit client selection in non-interactive runs, and complete credentials before writing. Tenant/project defaults are removed; startup release checks and new notification hooks now require explicit opt-in. Install uvx separately, and continue to use --guide when supplying a custom project guide.
Updating the npm package does not rewrite existing client files or installed hook scripts. Keep a private backup and rerun the installer for the clients you want to update. Supply --guide and --update-hook explicitly if those files should be installed or refreshed. Existing unrelated settings and hooks are preserved. See the README's upgrade instructions.
Changes
- Fix project-guide and hook installation in the ESM CLI and derive every version entry point from the package manifest or installed version marker.
- Validate affected configurations before writing; preserve unrelated client settings and refuse malformed JSON and unsafe file targets.
- Replace managed files atomically with private Unix permissions. Document plaintext credentials and the limits of Windows permissions and multi-file installation.
- Add explicit client selection, isolated configuration roots, environment/token-file input, and hidden interactive token entry. Non-interactive setup now requires
--agentand complete credentials. - Register guides only for selected Kiro clients, preserve unrelated startup hooks, and make release checks and new startup hooks opt-in.
- Remove tenant/project defaults and replace the project guide with a neutral template. Infer Confluence only for root Atlassian Cloud URLs.
- Include the license in npm archives and add cross-platform CI with isolated installer and packed-package regression tests.
Validation
18 installer and packed-package tests pass. The merged commit passed CI on Linux with Node.js 22/24 and macOS/Windows with Node.js 24. Published npm archive integrity and an isolated CLI version/help installation were verified before this GitHub release. Live Jira/MCP integration and multi-file rollback are outside this release's validation.
Source commit: e37b5f302bdf1f7e679d9079fa65dac368829fd9.
Install: npm install -g @andrekurait/jira-mcp-skill@2.0.0.
v1.0.5
- Add Jira wiki markup formatting section (use h2./h3., bold, {{code}}, avoid # for lists)
- Add refinement request output format for Slack (text + link separately)
v1.0.4
Improved
- Default Jira URL:
https://opensearch.atlassian.net - Default project key:
MIGRATIONS - Shows API token link before prompting
v1.0.3
Fixed
- Include README.md in npm package for proper display on npmjs.com
v1.0.2
Fixed
- Kiro hook configuration now uses correct agent config schema
- Hooks use
{ hooks: { agentSpawn: [...] } }format per Kiro docs - Creates
~/.kiro/agents/directory if it doesn't exist
Changed
- Version check hook runs on agent spawn (once per day)
- Outputs update notification to agent context if outdated
v1.0.1
Added
- Skill improvement protocol - AI asks to add rules permanently
- Step-by-step contribution guide (fork, branch, PR)
- Issue creation defaults table
- Example prompts → actions mapping
v1.0.0
Initial release
- One-command installer for mcp-atlassian
- Interactive and automatic modes
- Multi-agent support (Kiro, Claude, Cursor)
- MIGRATIONS project guide included
- Version check on startup