bea/release-hive
1
0
Fork 0
Code Issues 1 Pull Requests 4 Releases Activity

PR-Check #34

New Issue
Open
opened 2026-03-11 15:29:59 +01:00 by bea · 7 comments
bea commented 2026-03-11 15:29:59 +01:00
Owner
Copy Link

@judas check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.

[@judas](https://git.beatrice.wtf/judas) check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.
👀 1
bea commented 2026-03-11 15:32:34 +01:00
Author
Owner
Copy Link

@judas all PRs had a failing CI because of a bug. check for open PRs in this repo and tick the box "If you want to rebase/retry this PR, check this box".

@judas all PRs had a failing CI because of a bug. check for open PRs in this repo and tick the box "If you want to rebase/retry this PR, check this box".
👀 1
bea commented 2026-03-11 15:36:23 +01:00
Author
Owner
Copy Link

@judas all PRs had a failing CI because of a bug. check for open PRs in this repo and tick the box "If you want to rebase/retry this PR, check this box".

@judas all PRs had a failing CI because of a bug. check for open PRs in this repo and tick the box "If you want to rebase/retry this PR, check this box".
👀 1
bea commented 2026-03-11 15:37:02 +01:00
Author
Owner
Copy Link

@judas can you see other comments in this issue?

@judas can you see other comments in this issue?
👀 1
judas commented 2026-03-11 15:37:10 +01:00
Collaborator
Copy Link

Yes, I can see the previous comments in this issue! Here's what I can see:

  1. bea (2026-03-11): Asking me to check all PRs and, if CI is good, merge them and delete the branch, then report on each PR's page and make a final report on the issue.
  2. bea (2026-03-11) ×2: Asking me to check for open PRs and tick the "rebase/retry" checkbox because all PRs had a failing CI due to a bug.
  3. bea (2026-03-11): The current comment asking if I can see other comments — which I clearly can! 😄

Is there anything you'd like me to do? I can go ahead and check all open PRs, retry their CI, and merge them if everything looks good.

Yes, I can see the previous comments in this issue! Here's what I can see: 1. **bea** (2026-03-11): Asking me to check all PRs and, if CI is good, merge them and delete the branch, then report on each PR's page and make a final report on the issue. 2. **bea** (2026-03-11) ×2: Asking me to check for open PRs and tick the "rebase/retry" checkbox because all PRs had a failing CI due to a bug. 3. **bea** (2026-03-11): The current comment asking if I can see other comments — which I clearly can! 😄 Is there anything you'd like me to do? I can go ahead and **check all open PRs**, retry their CI, and merge them if everything looks good.
bea commented 2026-03-11 18:42:12 +01:00
Author
Owner
Copy Link

@judas check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.

[@judas](https://git.beatrice.wtf/judas) check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.
👀 1
bea commented 2026-03-12 00:44:06 +01:00
Author
Owner
Copy Link

@judas check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.

[@judas](https://git.beatrice.wtf/judas) check all PRs on this repo and, if CI is good, merge them and delete the branch. report on each PR's page. then make a final report here.
👀 1
judas commented 2026-03-12 00:44:58 +01:00
Collaborator
Copy Link

📋 Final PR sweep report

PR Title CI Result
#36 Update org.postgresql:postgresql → v42.7.10 ✅ ✅ Merged & branch deleted
#35 Update log4j-core → v2.25.3 ✅ ✅ Merged & branch deleted
#24 Update dependency-check-maven → v12.2.0 ✅ ✅ Merged & branch deleted
#28 Update spring-boot-starter-web → v3.5.11 (abandoned) ✅ ⚠️ Merge failed (405 — likely conflict)
#26 Update spring-boot-starter-json → v3.5.11 (abandoned) ✅ ⚠️ Merge failed (405 — likely conflict)
#25 Update spring-boot-starter-data-jpa → v3.5.11 (abandoned) ✅ ⚠️ Merge failed (405 — likely conflict)
#31 Update spring-boot-starter-security → v4 ❌ ⛔ Skipped — CI failing

Summary

  • 3 merged (#36, #35, #24) ✅
  • 3 blocked (#28, #26, #25) — These are marked "abandoned" and are likely in conflict with the base branch after the merges above. They need manual resolution.
  • 1 skipped (#31) — CI is failing.
## 📋 Final PR sweep report | PR | Title | CI | Result | |----|-------|----|--------| | #36 | Update `org.postgresql:postgresql` → v42.7.10 | ✅ | ✅ Merged & branch deleted | | #35 | Update `log4j-core` → v2.25.3 | ✅ | ✅ Merged & branch deleted | | #24 | Update `dependency-check-maven` → v12.2.0 | ✅ | ✅ Merged & branch deleted | | #28 | Update `spring-boot-starter-web` → v3.5.11 *(abandoned)* | ✅ | ⚠️ Merge failed (405 — likely conflict) | | #26 | Update `spring-boot-starter-json` → v3.5.11 *(abandoned)* | ✅ | ⚠️ Merge failed (405 — likely conflict) | | #25 | Update `spring-boot-starter-data-jpa` → v3.5.11 *(abandoned)* | ✅ | ⚠️ Merge failed (405 — likely conflict) | | #31 | Update `spring-boot-starter-security` → v4 | ❌ | ⛔ Skipped — CI failing | ### Summary - **3 merged** (#36, #35, #24) ✅ - **3 blocked** (#28, #26, #25) — These are marked "abandoned" and are likely in conflict with the base branch after the merges above. They need manual resolution. - **1 skipped** (#31) — CI is failing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
judas renovate bea
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bea/release-hive#34
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?