Skip to content

Conversation

@flowcore-machine
Copy link
Contributor

@flowcore-machine flowcore-machine commented Jan 20, 2026

🤖 I have created a release beep boop

1.2.5 (2026-01-20)

Bug Fixes

  • add nativeButton prop to Button components with render prop (e36b603)
  • prevent error information leakage in data sources page (2c07e89)

This PR was generated with Release Please. See documentation.

@github-actions
Copy link

github-actions bot commented Jan 20, 2026

📋 Approved Violation Exceptions

This PR can reference the following approved violation exceptions. Any violations matching these exceptions will be automatically waived during validation.

Total Active Exceptions: 0

No exceptions registry found.


💡 How Exception Validation Works:

  1. Validator checks if your code violation matches an exception in the table
  2. Verifies the commit SHA exists in this PR
  3. Fetches the detailed exception documentation from Usable
  4. Validates the exception has proper approval and justification
  5. If all checks pass, the violation is waived

📝 To add a new exception: Follow the guidelines in VIOLATION_EXCEPTIONS.md

🔄 This comment is automatically updated when VIOLATION_EXCEPTIONS.md changes

@github-actions
Copy link

github-actions bot commented Jan 20, 2026

🤖 Standards Validation

PR Validation Report

Summary

This is an automated release PR generated by Release Please. It bundles two bug fixes: one to prevent leaking error details on the data sources page, and another to improve the Button component's handling of non-native button elements like Next.js's <Link>. The changes are well-implemented, adhere to project standards, and improve both security and component architecture.

Critical Violations ❌

No critical violations found.

Important Issues ⚠️

No important issues found.

Suggestions ℹ️

No suggestions.

Validation Outcome

  • Status: PASS ✅
  • Critical Issues: 0
  • Important Issues: 0
  • Suggestions: 0

📊 Validation Statistics

@github-actions
Copy link

github-actions bot commented Jan 20, 2026

🤖 Security Validation

PR Validation Report

Summary

This Pull Request primarily focuses on a bug fix to prevent error information leakage within the data sources page. The changes involve utilizing a structured logging service for server-side error reporting, which enhances security by ensuring consistent and controlled error handling. The modifications to CHANGELOG.md and package.json do not introduce any security vulnerabilities.

Critical Security Vulnerabilities 🔴

None

High-Risk Security Issues 🟡

None

Security Improvements 🔵

  • Enhanced Server-Side Error Logging
    • Location: app/data-sources/page.tsx (lines 19, 35)
    • Enhancement: The change from direct console.error calls to logger.error (from @/lib/services/logger.service) for server-side error reporting. This ensures that error messages are handled by a structured logging service, which can format, redact, and route logs appropriately based on the environment (e.g., JSON in production).
    • Benefit: This improves the prevention of error information leakage by centralizing error handling and allowing for more controlled and secure logging, aligning with the principle of providing generic error messages to users while logging detailed errors server-side.

Security Standards References

  • Next.js 15 Performance & Security Guidance (fragmentId: 34871d5b-631a-48e5-a557-18487843b56a) - Consulted for general Next.js security practices.
  • NextJS 15 API Development - Critical LLM Rules (fragmentId: 2d6faeb9-e809-4743-8962-7ebb28103841) - Consulted for API development security rules.
  • General security best practices regarding error handling and information leakage.

Security Violation Exceptions Applied

No exceptions applied.

Validation Outcome

  • Status: PASS ✅
  • Critical Vulnerabilities: 0
  • High-Risk Issues: 0
  • Security Improvements: 1
  • Exceptions Applied: 0

See the pinned "📋 Approved Violation Exceptions" comment for the full exceptions registry
Validated against security best practices from Usable workspace
Generated by Gemini CLI + Usable MCP


📊 Validation Statistics

@blacksmith-sh

This comment has been minimized.

@flowcore-machine flowcore-machine force-pushed the release-please--branches--main--components--graphable branch from 6bf5e0a to 87b9d1f Compare January 20, 2026 17:28
@suuunly suuunly merged commit 41c0d4a into main Jan 20, 2026
5 checks passed
@suuunly suuunly deleted the release-please--branches--main--components--graphable branch January 20, 2026 17:31
@flowcore-machine
Copy link
Contributor Author

🤖 Created releases:

🌻

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants