Skip to content

Release: staging -> main (2026-04-20 04:51)#546

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
staging
Closed

Release: staging -> main (2026-04-20 04:51)#546
github-actions[bot] wants to merge 1 commit into
mainfrom
staging

Conversation

@github-actions

Copy link
Copy Markdown

Summary

Promotes staging into main.

  • Source branch: staging
  • Target branch: main
  • Generated by npm run pr:promote

Included PRs

  • No merged PRs were detected automatically.

Compare

chore: sync main into staging
@github-actions github-actions Bot added automated Automated main-to-staging sync PR release Release promotion PR labels Apr 20, 2026
@greptile-apps

greptile-apps Bot commented Apr 20, 2026

Copy link
Copy Markdown
Contributor

No reviewable files after applying ignore patterns.

@vercel

vercel Bot commented Apr 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
open-shelf Ignored Ignored Apr 20, 2026 4:52am

@codecov

codecov Bot commented Apr 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@is0692vs

Copy link
Copy Markdown
Contributor

Closing this release PR to satisfy the current staging-only open PR policy for this sweep. Main sync was already merged via #521.

@is0692vs

Copy link
Copy Markdown
Contributor

Closed to keep only staging-target PRs open after main integration via #521.

@is0692vs is0692vs closed this Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated main-to-staging sync PR release Release promotion PR size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant