Skip to content

Conversation

@vaind
Copy link
Contributor

@vaind vaind commented Sep 24, 2025

Summary

  • Fix changelog-entry boolean evaluation to properly check 'true' vs 'false' strings instead of relying on truthy evaluation
  • Add input validation for changelog-entry to only allow 'true' or 'false' values
  • Add input validation for pr-strategy to only allow 'create' or 'update' values

Test plan

  • Test with changelog-entry: 'true' - should work as before
  • Test with changelog-entry: 'false' - should now properly skip changelog step
  • Test with invalid changelog-entry value - should fail early with clear error
  • Test with invalid pr-strategy value - should fail early with clear error

🤖 Generated with Claude Code

vaind and others added 2 commits September 24, 2025 21:58
- Fix changelog-entry boolean evaluation to properly check 'true' vs 'false' strings
- Add input validation for changelog-entry to only allow 'true' or 'false'
- Add input validation for pr-strategy to only allow 'create' or 'update'

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@vaind vaind merged commit 15e4b10 into main Sep 24, 2025
17 checks passed
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.

2 participants