Fix label field length validation to match api - #413
Open
IainSteers wants to merge 2 commits into
Open
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
soumyas-dev
added a commit
that referenced
this pull request
Jun 9, 2026
srinivasgowda097
added a commit
that referenced
this pull request
Jun 9, 2026
Fix label field length validation to match api(#413)
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
1 participant
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.
The catalog label name and description length limits are too small and do not match the constraints of the JFrog Curation API.
The current API limits can be seen in https://docs.jfrog.com/security/docs/graphql-apis#graphql-api-error-messages
I've also confirmed the updated resource works against a dev install of artifactory and curation.
Closes #403