chore(deps): bump rift engine to 0.19.0 - #257
Merged
Merged
Conversation
Bumps the rift engine pin from 0.18.1 to 0.19.0 via scripts/bump.sh (the single source of truth for this repo's pin literals).
rift 0.19.0 made DELETE savedProxyResponses also delete the stubs a proxy recorded (recordedFrom), matching Mountebank. The Reset policy clears proxy responses before each test, so on the golden imposter it deleted the golden fixture itself: REPLAY served nothing and CAPTURE kept only the last test. Spare the golden imposter proxy responses on reset and document the engine change on Imposter.clearProxyResponses and in the JUnit 5 guide.
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.
SDK fix for a 0.19.0 behaviour change (commit 4a68ca8)
The first run failed
RiftGoldenIT.goldenCaptureThenReplayin the REPLAY step. rift 0.19.0 (#1239) madeDELETE /imposters/{port}/savedProxyResponsesalso delete the stubs a proxy recorded (recordedFrom), which matches Mountebank'sdeleteSavedProxyResponses. The JUnit 5Resetpolicy callsclearProxyResponses()before every test. On the@RiftGoldenimposter, that call deleted the golden fixture: REPLAY served nothing, and CAPTURE would have kept only the last test method's recordings.RiftTestContext.resetConfiguredImposters()no longer clears proxy responses on the golden imposter. Recorded requests and scenario state are still reset, and other imposters are unchanged.RiftGoldenUnitTest.perTestResetKeepsTheGoldenImpostersRecordedStubs(fake admin) plusRiftGoldenIT, which now runs two tests per fixture (capture accumulates, replay survives reset).Imposter.clearProxyResponsesjavadoc anddocs/junit5.md. User-visible: on rift >= 0.19.0 aPER_TESTreset now makes a plainrecord()imposter re-reach its upstream.Engine verdict: 0.19.0 is correct, so the fix belongs in the SDK.
Bumps the pinned rift engine version from
0.18.1to0.19.0viascripts/bump.sh.Upstream release notes (achird-labs/rift 0.19.0)
Rift v0.19.0
Rift is a high-performance, Mountebank-compatible HTTP chaos engineering proxy.
Installation
Quick Install (Unix)
Using Docker
Using Cargo
Included Binaries
Each release archive includes all Rift tools:
rift- HTTP proxy server (Mountebank-compatible)rift-lint- Imposter configuration validatorrift-tui- Terminal UI for managing impostersrift-verify- Stub verifier (checks imposters against a running engine)Available Platforms
rift-v0.19.0-x86_64-unknown-linux-gnu.tar.gzrift-v0.19.0-aarch64-unknown-linux-gnu.tar.gzrift-v0.19.0-x86_64-unknown-linux-musl.tar.gzrift-v0.19.0-aarch64-unknown-linux-musl.tar.gzrift-v0.19.0-x86_64-apple-darwin.tar.gzrift-v0.19.0-aarch64-apple-darwin.tar.gzrift-v0.19.0-x86_64-pc-windows-msvc.zipDocker Images
zainalpour/rift-proxyzainalpour/rift-lintFeatures
All binaries include:
Verification
Each binary has an accompanying
.sha256checksum file. Verify downloads with:Mountebank Compatibility
Rift is API-compatible with Mountebank:
Documentation
Full-auto loop: when CI is green, the repo's
auto-release.ymlmerges this PR andcuts the next release. If CI is red, this PR stays open for human intervention. Opened
automatically by the reusable dep-bump workflow.
🤖 Generated with Claude Code