modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
0 releases 36 tags
  • v1.4.0 731198572b

    Set 429 status code responses in the config map (#849)

    Ghost released this 2025-12-13 20:34:12 +00:00 | 251 commits to main since this release

    Motivation and Context

    Seems that per ingress annotations were not working, so had to put them
    in the ingress configmap. Did tested this manually on staging so it's
    confirmed it's working (I was getting 429s instead of 503s) and no
    traffic was getting into the registry pod.

    How Has This Been Tested?

    Breaking Changes

    Types of changes

    • Bug fix (non-breaking change which fixes an issue)
    • New feature (non-breaking change which adds functionality)
    • Breaking change (fix or feature that would cause existing
      functionality to change)
    • Documentation update

    Checklist

    • I have read the MCP
      Documentation
    • My code follows the repository's style guidelines
    • New and existing tests pass locally
    • I have added appropriate error handling
    • I have added or updated documentation as needed

    Additional context

    Signed-off-by: Radoslav Dimitrov radoslav@stacklok.com

    Downloads