Repository navigation
chore: bump agent config schema version - #1878
Merged
Merged
Conversation
TimPansino
approved these changes
Oct 8, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1878 +/- ##
==========================================
- Coverage 82.01% 81.77% -0.24%
==========================================
Files 223 223
Lines 28032 28013 -19
Branches 4436 4433 -3
==========================================
- Hits 22991 22909 -82
- Misses 3476 3553 +77
+ Partials 1565 1551 -14 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Auto-generated bump PR.
Bump computed from the schema diff since
v13.6.1.Merge this PR BEFORE cutting the release tag.
If the release tag is cut before this PR merges, the tag's
configurationDefinitions.ymlwill still reflect thepre-bump version even though the schema itself reflects the
new keys. Consumers see a mismatch.