Repository navigation
Pin the MCP image to the public 0.2.1 release - #40
Merged
Merged
Conversation
The private-registry sha was an interim default until openops-mcp had a public release. 0.2.1 is that release, and it carries the fix that lets the MCP server reach the API through its internal URL instead of the public issuer. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
MarceloRGonc
approved these changes
Sep 22, 2026
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
2 participants
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.
Fixes OPS-4867.
What
mcp.repository→openops.azurecr.io,mcp.tag→0.2.1, replacing the interim private-registry sha8e7c930f. This follows the convention already used for the other independently versioned images (Tables, Analytics): public registry plus release version.Why
openops-mcp0.2.1 is the first public release with the OPS-4866 fix: the MCP server fetches the JWKS and calls the token endpoint through the internalOPENOPS_API_URLinstead of the public issuer. Without it, an install whose public URL is not reachable from inside the cluster (for examplehttp://localhost) rejects every MCP token.Targets
mg/OPS-4456because that branch publishes the0.6.26-draftchart the internal deploys use. After merge, re-run the release workflow (draft) so the draft chart picks up the new default; dev then inherits it with no devops change.Testing
helm lint chartpasses;helm templatewithvalues.ci.yamlandvalues.mcp-example.yamlrendersopenops.azurecr.io/openops-mcp:0.2.1.1c45ccf5) is running on dev AKS via a values override and re-authentication from Claude Code succeeds.🤖 Generated with Claude Code