Bu fixes

[yehlo]

Description

What does this PR do?

Why is this change needed?

Related Issues

• Related to: #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📚 Documentation update
• ♻️ Refactoring (no functional changes)
• ✅ Test updates (adding or updating tests)
• 🔧 Configuration changes
• 🚀 Performance improvements
• 🎨 Style changes (formatting, naming, etc.)
• 📦 Dependency updates
• 🔨 CI/CD changes

Conventional Commit Format

Your PR title should follow this format:

<type>(<scope>): <description>

Examples:
  feat(auth): add OAuth2 authentication support
  fix(api): resolve null pointer exception in user service
  docs(readme): update installation instructions
  chore(deps): bump typescript from 5.0.0 to 5.1.0

Common types:

• feat: - New feature (minor version bump)
• fix: - Bug fix (patch version bump)
• docs: - Documentation changes
• refactor: - Code refactoring (no functional changes)
• test: - Adding/updating tests
• chore: - Maintenance tasks (dependencies, build, CI/CD)
• perf: - Performance improvements

Breaking changes:

feat(api)!: remove deprecated v1 endpoints

BREAKING CHANGE: v1 API endpoints have been removed.
See MIGRATION.md for upgrade guide.

Testing Checklist

• Tests added or updated
• All existing tests pass locally
• Manual testing performed
• Test coverage maintained or improved

Test commands run:

# Commands you ran locally to verify your changes
# (Automated CI tests will run automatically on PR submission)
make test
make lint

Test results:

Documentation Checklist

• README.md updated (if user-facing changes)
• Documentation updated (if applicable)
• Code comments added for complex logic
• CRD / API documentation updated (if API or type changes)

Security Checklist

• No secrets or credentials committed
• Input validation implemented where needed
• Security implications considered and documented
• Dependencies scanned for vulnerabilities
• Authentication/authorization logic reviewed
• Error messages don't leak sensitive information

Breaking Changes

Does this PR introduce breaking changes?

• Yes
• No

If yes, describe the breaking changes and migration path:

Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or my feature works
• New and existing tests pass locally with my changes
• Any dependent changes have been merged and published
• PR title follows Conventional Commits format

Additional Context

Reviewer Notes:

Follow-up Work: