chore: Add Citrus to 4.10.1#92
Merged
Merged
Conversation
- Includes updated field schema descriptions for Citrus custom fields (such as EndpointField)
📝 WalkthroughWalkthroughThis PR adds a new Citrus 4.10.1 catalog version with comprehensive JSON schemas defining agent configuration, test functions, test containers, and validation matchers. The new version is registered in catalog index files. ChangesCitrus 4.10.1 Catalog Registration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@catalog/citrus/4.10.1/citrus-agent-configuration.json`:
- Around line 61-66: The JSON Schema defaults for several properties are strings
instead of matching their declared types; update each property's "default" to
the correct JSON type (e.g., change "default": "true"/"false" to true/false for
properties with "type": "boolean", and change numeric-string defaults to numbers
for "type": "integer"). Specifically fix the "offline" property and the other
schema entries flagged in the comment so their "default" values are actual
booleans or integers rather than quoted strings, preserving existing semantics
but using the correct JSON types.
In `@catalog/citrus/4.10.1/citrus-catalog-aggregate-functions.json`:
- Line 1055: Update the user-facing description strings in
citrus-catalog-aggregate-functions.json that currently read "When enabled the
read file content is converted into bas64." to use the correct spelling "base64"
instead; locate the affected "description" properties (the ones describing
read-file content conversion) and replace "bas64" with "base64" in both
occurrences so generated docs/forms show the correct term.
In `@catalog/citrus/4.10.1/citrus-catalog-aggregate-test-containers.json`:
- Around line 248-255: Several schema properties declared as "integer" or
"boolean" currently have string defaults; update their "default" values to the
correct JSON types: change iterate.startsWith and iterate.step defaults from "1"
to the number 1, change repeat.startsWith and repeatOnError.startsWith defaults
from "1" to 1, change timer.interval default from "1000" to the number 1000, and
change timer.autoStop and timer.fork defaults from "true"/"false" to the
booleans true/false respectively; locate these properties by their names
(iterate.startsWith, iterate.step, repeat.startsWith, repeatOnError.startsWith,
timer.interval, timer.autoStop, timer.fork) and replace the quoted string
defaults with unquoted numeric or boolean literals so the defaults match the
declared "integer" or "boolean" types.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6b9f9982-0355-4091-9815-ec438031072a
📒 Files selected for processing (11)
catalog/citrus/4.10.1/citrus-agent-configuration.jsoncatalog/citrus/4.10.1/citrus-catalog-aggregate-endpoints.jsoncatalog/citrus/4.10.1/citrus-catalog-aggregate-functions.jsoncatalog/citrus/4.10.1/citrus-catalog-aggregate-test-actions.jsoncatalog/citrus/4.10.1/citrus-catalog-aggregate-test-containers.jsoncatalog/citrus/4.10.1/citrus-catalog-aggregate-validation-matcher.jsoncatalog/citrus/4.10.1/citrus-testcase.jsoncatalog/citrus/4.10.1/citrus-testcase.xsdcatalog/citrus/4.10.1/index.jsoncatalog/index.jsonindex.js
lordrip
approved these changes
May 8, 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.
Summary by CodeRabbit