Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docker-wordpress-php images #641

Merged
merged 2 commits into from
Nov 8, 2023
Merged

Conversation

joehoyle
Copy link
Member

@joehoyle joehoyle commented Nov 6, 2023

8.2.11

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/8.2.10...8.2.11

8.2.10

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/8.2.9...8.2.10

6.0.12

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/6.0.11...6.0.12

6.0.11

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/6.0.10...6.0.11

5.0.12

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/5.0.11...5.0.12

5.0.11

What's Changed

Full Changelog: https://github.com/humanmade/docker-wordpress-php/compare/5.0.10...5.0.11

# 8.2.10

## What's Changed
* [Backport v8.2-branch] Bump php from 8.2.11-fpm-bookworm to 8.2.12-fpm-bookworm by @hm-backport in humanmade/docker-wordpress-php#247
* [Backport v8.2-branch] Update Afterburner 0.4.5 -> 0.4.6 by @hm-backport in humanmade/docker-wordpress-php#251


**Full Changelog**: humanmade/docker-wordpress-php@8.2.9...8.2.10

# 6.0.11

## What's Changed
* [Backport v6.0-branch] Update Afterburner 0.4.5 -> 0.4.6 by @hm-backport in humanmade/docker-wordpress-php#250


**Full Changelog**: humanmade/docker-wordpress-php@6.0.10...6.0.11

# 5.0.11

## What's Changed
* [Backport v5.0-branch] Update Afterburner 0.4.5 -> 0.4.6 by @hm-backport in humanmade/docker-wordpress-php#249


**Full Changelog**: humanmade/docker-wordpress-php@5.0.10...5.0.11
@joehoyle joehoyle requested a review from a team November 6, 2023 12:15
Copy link
Contributor

@wisyhambolu wisyhambolu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@joehoyle joehoyle merged commit 541c7fc into master Nov 8, 2023
1 of 2 checks passed
@joehoyle joehoyle deleted the docker-wordpress-php-update branch November 8, 2023 09:59
@hm-backport
Copy link

hm-backport bot commented Nov 8, 2023

The backport to v16-branch failed:

Commits ["4849f53b0127bc43e24907bee0b8427deb7b28f0","68681adb872e9294dab615cf816300514a0ed897"] could not be cherry-picked on top of v16-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v16-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 4849f53b0127bc43e24907bee0b8427deb7b28f0 68681adb872e9294dab615cf816300514a0ed897
# Create a new branch with these backported commits.
git checkout -b backport-641-to-v16-branch
# Push it to GitHub.
git push --set-upstream origin backport-641-to-v16-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

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

@hm-backport
Copy link

hm-backport bot commented Nov 8, 2023

The backport to v17-branch failed:

Commits ["4849f53b0127bc43e24907bee0b8427deb7b28f0","68681adb872e9294dab615cf816300514a0ed897"] could not be cherry-picked on top of v17-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v17-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 4849f53b0127bc43e24907bee0b8427deb7b28f0 68681adb872e9294dab615cf816300514a0ed897
# Create a new branch with these backported commits.
git checkout -b backport-641-to-v17-branch
# Push it to GitHub.
git push --set-upstream origin backport-641-to-v17-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

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

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