Skip to content

fix: release id parsing for external release targets - #21

Merged
SecondSkoll merged 1 commit into
mainfrom
docs/update-refs
Aug 14, 2026
Merged

fix: release id parsing for external release targets#21
SecondSkoll merged 1 commit into
mainfrom
docs/update-refs

Conversation

@SecondSkoll

Copy link
Copy Markdown
Owner

No description provided.

@SecondSkoll
SecondSkoll merged commit e33969f into main Aug 14, 2026
2 checks passed

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SecondSkoll, the release ID documentation is updated consistently with the string input schema. One wording change would make the accepted format less ambiguous.

release_id:
description: Positive GitHub release ID. Exactly one of release_id/release_tag is required.
type: number
description: Positive decimal GitHub release ID. Exactly one of release_id/release_tag is required.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SecondSkoll, “decimal” could be read as allowing fractional values, while the validation accepts only positive integers. Please describe this as a base-10 integer, consistently with the validation comment and configuration reference.

Suggested change
description: Positive decimal GitHub release ID. Exactly one of release_id/release_tag is required.
description: Positive base-10 integer GitHub release ID. Exactly one of release_id/release_tag is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant