ginee-file-framework-bug

To file an upstream framework bug, you draft a structured issue using the framework-bug-report template and submit it to the configured upstream framework-repo. This ensures core component defects are tracked officially rather than in adopter projects.

A framework bug report requires the affected framework artefact, framework version, adapter in use, reproduction steps, expected versus actual results, blocking severity, and optional owner-history pointers to ensure compliant upstream issue submission.

You should report a defect to the framework upstream when the issue lies in the core or framework components themselves, not in your specific adopter project configuration, ensuring the defect is tracked in the official system.

The outbound issue workflow handles framework version and adapter tracking by automatically populating these fields within the framework-bug-report template, ensuring the upstream repository receives all critical environmental context.

Yes, you can submit blocking severity issues directly to the framework upstream. The bug report template includes a specific blocking severity field to prioritize and communicate the defect's impact to the upstream maintainers.