Skip to content

Conversation

pquentin
Copy link
Member

@pquentin pquentin commented Sep 26, 2025

Copy link
Contributor

Following you can find the validation changes against the target branch for the API.

API Status Request Response
search 🔴 2559/2637 → 2567/2637 2637/2637

You can validate this API yourself by using the make validate target.

@l-trotta
Copy link
Contributor

nicely done with the docs and defaults!

@pquentin pquentin merged commit 2cddbef into main Sep 29, 2025
14 checks passed
@pquentin pquentin deleted the p-value-heuristics branch September 29, 2025 09:42
Copy link
Contributor

The backport to 8.19 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-5353-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2cddbefb265a4cffdcff8c2b6c29561429d8a499
# Push it to GitHub
git push --set-upstream origin backport-5353-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19

Then, create a pull request where the base branch is 8.19 and the compare/head branch is backport-5353-to-8.19.

Copy link
Contributor

The backport to 9.0 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.0 9.0
# Navigate to the new working tree
cd .worktrees/backport-9.0
# Create a new branch
git switch --create backport-5353-to-9.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2cddbefb265a4cffdcff8c2b6c29561429d8a499
# Push it to GitHub
git push --set-upstream origin backport-5353-to-9.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.0

Then, create a pull request where the base branch is 9.0 and the compare/head branch is backport-5353-to-9.0.

Copy link
Contributor

The backport to 9.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-9.1 9.1
# Navigate to the new working tree
cd .worktrees/backport-9.1
# Create a new branch
git switch --create backport-5353-to-9.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2cddbefb265a4cffdcff8c2b6c29561429d8a499
# Push it to GitHub
git push --set-upstream origin backport-5353-to-9.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-9.1

Then, create a pull request where the base branch is 9.1 and the compare/head branch is backport-5353-to-9.1.

pquentin added a commit that referenced this pull request Sep 29, 2025
pquentin added a commit that referenced this pull request Sep 29, 2025
(cherry picked from commit 2cddbef)

# Conflicts:
#	output/schema/schema.json
pquentin added a commit that referenced this pull request Sep 29, 2025
(cherry picked from commit 2cddbef)

# Conflicts:
#	output/schema/schema.json
@pquentin
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
9.1
9.0
8.19

Questions ?

Please refer to the Backport tool documentation

pquentin added a commit that referenced this pull request Sep 29, 2025
(cherry picked from commit 2cddbef)

# Conflicts:
#	output/schema/schema.json
pquentin added a commit that referenced this pull request Sep 29, 2025
(cherry picked from commit 2cddbef)

# Conflicts:
#	output/schema/schema.json
pquentin added a commit that referenced this pull request Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants