fix(ci): run validate-release on pull_request events

[omrdev1]

Problem

validate-release was permanently showing "Expected — Waiting for status to be reported" on every PR because the workflow only triggered on push to main and tags — never on pull_request events.

This meant the required status check could never go green, forcing every PR to use bypass rules to merge.

Fix

Add pull_request: branches: [main] trigger to release-check.yml so CI actually runs on PRs and the status check can resolve.

[github-actions]

🌱 GreenOps Infrastructure Impact

Total Current Footprint: 7.06kg CO2e/month | $126.29/month
Potential Savings: -2.60kg CO2e/month (36.8%) | -$13.87/month
💡 Found 2 optimization recommendations.

Resource Breakdown

Resource	Type	Region	CO2e/month	Cost/month	Action
aws_instance.web	m5.large	us-east-1	4.31kg	$70.08	💡 View Recommendation
aws_instance.worker	m6g.large	us-east-1	2.74kg	$56.21	💡 View Recommendation

Recommendations

aws_instance.web

• Current: m5.large in us-east-1
• Suggested: m6g.large in us-east-1
• Impact: -1.57kg CO2e/month | -$13.87/month
• Rationale: Switching from m5.large (x86_64) to m6g.large (ARM64) provides identical vCPU and memory at lower power draw, reducing carbon by 1570g CO2e/month and cost by $13.87/month.

aws_instance.worker

• Current: m6g.large in us-east-1
• Suggested: m6g.large in us-west-2
• Impact: -1.03kg CO2e/month | +$0.00/month
• Rationale: Moving m6g.large from us-east-1 to US West (Oregon) (us-west-2) reduces grid carbon intensity from 384.5g to 240.1g CO2e/kWh, saving 1030g CO2e/month saving $0.00/month.

---

Emissions calculated using the Open GreenOps Methodology Ledger (v1.1.0). Scope 2 operational emissions only — embodied carbon and water are not tracked. Math is MIT-licensed and auditable. Analysed at 2026-03-27T08:13:09.830Z. Learn more.

🏢 Managing green-ops across dozens of repositories? Upgrade to GreenOps Dashboard to aggregate CI/CD carbon data natively.