Skip to content

Staging - #335

Open
glikely wants to merge 1 commit into
mainfrom
staging
Open

Staging#335
glikely wants to merge 1 commit into
mainfrom
staging

Conversation

@glikely

@glikely glikely commented Aug 8, 2026

Copy link
Copy Markdown
Owner

No description provided.

@EdueskaWeiz

Copy link
Copy Markdown
Contributor

Heads-up: both commits here are already on main. d21b23e is patch-identical to ffe62a2, and 8799eba to b2e0ed1 — I diffed the pairs and they match exactly. They landed when you closed #333, about fifteen minutes after this PR was opened, so this branch is likely just stale.

Merging would not undo anything, since the merge base predates those commits and both sides changed the same files to the same content. It would only add duplicate history.

One thing worth checking before the release: main differs from this branch in buildspec.json and .github/workflows/build-project.yaml — the OBS 32.2.1 dependency bump and the macos-26 runner change. Both are on main, neither is here.

@glikely

glikely commented Aug 8, 2026

Copy link
Copy Markdown
Owner Author

Heads-up: both commits here are already on main. d21b23e is patch-identical to ffe62a2, and 8799eba to b2e0ed1 — I diffed the pairs and they match exactly. They landed when you closed #333, about fifteen minutes after this PR was opened, so this branch is likely just stale.

You can safely ignore this PR. I used it for testing to make sure that when I reordered the patches I didn't break bisecting. After the build completed here I pushed the full series out to main

@glikely
glikely force-pushed the staging branch 2 times, most recently from 6ff6b8d to 15a4486 Compare August 9, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants