Remove unused updater timeout fixture - #1756
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Removes an obsolete updater timeout field from test fixture data to match the current job contract.
Changes:
- Removes the unused
max-updater-run-timefixture property.
Show a summary per file
| File | Description |
|---|---|
__tests__/server/db.json |
Aligns the fake job response with the supported contract. |
Review details
Tip
Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
markhallen
approved these changes
Aug 12, 2026
Merged
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.
Remove the unused
max-updater-run-timefield from the fake job-details response.The action does not declare or consume this field, so this only updates test data to match the current job contract.
Validated with Node 24.13.0:
npm run format-checknpm run lint-checknpm run typechecknpm test(134 passed, 17 skipped)npm run packagePackaging produced no tracked
distchanges.Related: