Conversation
jira-mcp was renamed ujira, crate and repo. The broker pinned v0.4.0 under the old name; v0.7.0 keeps the Access/Config/JiraClient/render surface the broker embeds, so only the name moves. Assisted-by: Claude
|
Docs preview for this PR is built and attached as the Download Rebuilt for c1a7bed. |
wseaton
enabled auto-merge
September 23, 2026 03:35
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
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.
The broker embedded
jira-mcpv0.4.0, which has since been renamedujira(crate and repo). This moves it to ujira v0.7.0, the latest release and the version the sandbox images already ship as the standalone MCP server. The embedded surface (Access,Config,JiraClient,render) is unchanged, so only the dependency name moves;deny.toml's allow-git entry follows it.Broker tests (184) and clippy pass,
cargo deny checkis clean, and the dep-dup guard reports nothing new.