chore(rate-limiter): bump cpex_rate_limiter to 0.0.4 - #47
Merged
Merged
Conversation
gandhipratik203
requested review from
lucarlig and
msureshkumar88
as code owners
April 22, 2026 09:00
gandhipratik203
force-pushed
the
bump/rate-limiter-v0.0.4
branch
2 times, most recently
from
April 22, 2026 09:26
52833fd to
7693501
Compare
gandhipratik203
had a problem deploying
to
testpypi
April 22, 2026 09:37 — with 
GitHub Actions
Failure
GitHub Actions
Failure
gandhipratik203
had a problem deploying
to
testpypi
April 22, 2026 09:37 — with
GitHub Actions
Failure
GitHub Actions
Failure
lucarlig
approved these changes
Apr 22, 2026
Bumps the declared version of cpex_rate_limiter from 0.0.3 to 0.0.4.
Version-bearing files (coupled via tools/plugin_catalog.py release_info
enforcement that tag version == Cargo/manifest version):
- plugins/rust/python-package/rate_limiter/Cargo.toml
- plugins/rust/python-package/rate_limiter/cpex_rate_limiter/plugin-manifest.yaml
- Cargo.lock (auto-updated)
- tests/test_plugin_catalog.py (2 release-info
tests that validate the rate_limiter canonical tag)
Because release-validation / resolve validates the plugin referenced by
the ci-yaml `tag:` input (via release_info reading the PR-head Cargo),
the bump of rate_limiter breaks the prior sentinel. Rotate both PR-
triggered release-validation calls off rate-limiter onto a stable
already-released sentinel. retry-with-backoff-v0.1.1 was chosen because
(a) its Cargo on main matches the tag version, and (b) it has not been
used as a PR-smoke sentinel before, so the test.pypi publish path
produces a fresh upload rather than colliding on content hash with a
prior repeated sentinel upload:
- .github/workflows/ci-rust-python-package.yaml (tag: retry-with-backoff-v0.1.1)
- .github/workflows/ci-install-built-wheel.yaml (tag: retry-with-backoff-v0.1.1)
- tests/test_plugin_catalog.py (generated-
workflow assertion updated to match)
Naming-example references in DEVELOPING.md, README.md, and AGENTS.md
continue to use rate-limiter-v0.0.2 as their illustrative placeholder
and are intentionally not touched.
Local gate:
python3 -m unittest tests.test_plugin_catalog → 71 passed
Signed-off-by: Pratik Gandhi <gandhipratik203@gmail.com>
gandhipratik203
force-pushed
the
bump/rate-limiter-v0.0.4
branch
from
April 22, 2026 09:53
7693501 to
14ca7ca
Compare
gandhipratik203
temporarily deployed
to
testpypi
April 22, 2026 12:24 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
gandhipratik203
temporarily deployed
to
testpypi
April 22, 2026 12:40 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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
3 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.
Summary
Bumps
cpex_rate_limiterfrom 0.0.3 → 0.0.4 so the production-hardening fixes in #40 can be consumed downstream. PyPI 0.0.3 is already published and immutable, so a version bump is required for the main repo (mcp-context-forge) to pick up the fixes.CI sentinel rotation
release-validation / resolvein the called release workflow enforcestag version == Cargo/manifest version(viatools/plugin_catalog.py::release_info). The PR-triggered smoke test was usingrate-limiter-v0.0.3as its sentinel, which now mismatches because this PR raises rate_limiter to 0.0.4.This PR rotates the sentinel in
ci-rust-python-package.yamlandci-install-built-wheel.yamloff the plugin being bumped, ontopii-filter-v0.2.1(the most recently published tag whose Cargo onmainstill matches). This keeps release-validation meaningful (it still replays a real released tag) without coupling it to the plugin currently being bumped. Every future bump of a sentinel plugin will need the same rotation.Files touched
plugins/rust/python-package/rate_limiter/Cargo.toml— 0.0.3 → 0.0.4plugins/rust/python-package/rate_limiter/cpex_rate_limiter/plugin-manifest.yaml— 0.0.3 → 0.0.4Cargo.lock— auto-updated.github/workflows/ci-rust-python-package.yaml— sentinel →pii-filter-v0.2.1.github/workflows/ci-install-built-wheel.yaml— sentinel →pii-filter-v0.2.1tests/test_plugin_catalog.py— 2 release-info tests updated torate-limiter-v0.0.4, generated-workflow assertion updated topii-filter-v0.2.1Local verification
Post-merge
Tag
mainHEAD asrate-limiter-v0.0.4; the tag push triggers the release workflow and publishes the wheel to PyPI. The main repo (mcp-context-forge) can then pincpex-rate-limiter==0.0.4to consume #40's fixes.