Test

[Codewithspike]

Issue

Closes #(Issue number here - REQUIRED)

Description

Please describe your changes and why you're making them.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Performance improvement
• Refactoring
• Security update

How Has This Been Tested?

Please describe how you've tested these changes:

• Unit tests
• Integration tests
• Manual testing
• Other (please describe):

Screenshots or Videos (if applicable)

If your changes involve UI or significant behavior changes, please add screenshots or videos here.

Checklist

Before submitting, please ensure:

• I have read the CONTRIBUTING.md guidelines
• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation if needed
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests passed locally
• My branch name follows the pattern: feature/issue-<num>-<description> or fix/issue-<num>-<description>
• My commits are well-formatted with descriptive messages (e.g., feat(issue-45): add new feature)
• I assigned myself to the related issue using /assign @username in the issue discussion (NOT in this PR)

Related Issues or Discussions

Add any related issue numbers or discussions here (e.g., Related to #123)

Additional Context or Notes

Add any additional context or notes that might be helpful for reviewers.

[github-actions]

📋 PR Metadata Check:

❌ Issue Link
✅ Description (50+ chars)
✅ Type of Change Section
✅ Checklist

Please ensure all sections are completed. Review the PR template.

[github-actions]

⚠️ Commit Message Format Issues Found:

Commits must follow the format: type(issue-#): description

Invalid Commits:

• Commit Merge feature/test into main: Completed Frontend Deployment and user setup #1: update(workers): Updated Admin Action Integration
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit Combine build workers, clone updates, frontend rename, and API changes #2: update(workers): Updated Admin Action Integration
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit Logger added with Kafka and clickhouse #3: feat: refactor URL handling and build process with enhanced configuration and Docker integration
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit Consolidate Queues, Introduce Pub-Sub, and Refactor Build Architecture #4: update(workers): Updated Admin Action Integration >< README.md
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit Welcome to veren Discussions! #5: >< README.md
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit fix: rename publilishEvent to publishEvent across codebase #6: Publisher naming convention changed.
  Expected format: feat(issue-123): description or fix(issue-456): description
• Commit [Bug/Enhancement] Missing Graceful Shutdown #7: update(workers): Updated Admin Action Integration >< README.md
  Expected format: feat(issue-123): description or fix(issue-456): description

Valid Types: feat, fix, docs, style, refactor, perf, test, chore
Example: feat(issue-45): add new authentication endpoint

Please see CONTRIBUTING.md for detailed guidelines.

[github-actions]

🚫 Branch Protection: This PR targets main. All changes must go through the test branch first.

Action Required:

1. Close this PR
2. Create a new PR targeting the test branch
3. Once merged to test, create a release PR from test to main

Note: Only authorized admins can create PRs to main.

See CONTRIBUTING.md for details.

[github-actions]

🔒 Security Audit: Dependencies have been checked for known vulnerabilities. Address any critical or high-severity issues before merge. See SECURITY.md for guidelines.

[github-actions]

🏗️ Build Verification: Build checks have been executed for all services. Ensure your changes compile correctly before requesting review.

[github-actions]

✅ Code Quality Checks: TypeScript compilation and linting checks completed. Please ensure no breaking TypeScript errors are present before requesting review.