Conversation
This was referenced Jun 26, 2025
Member
Author
|
Updated the release date + added mention of this also affecting Magento setups. @Potherca Any objections ? If I don't hear from you within the next 12 hours, I'll proceed with the release anyhow as this fix needs to get out. |
Includes minor touching up of some headers and fixing a couple of broken links in the changelog file.
07716f8 to
d969990
Compare
Potherca
approved these changes
Jun 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Includes minor touching up of some headers and fixing a couple of broken links in the changelog file.
Release checklist
General
composer.json- PR Composer: bump PHP Parallel Lint #238Release Preparation
CHANGELOG.mdfile based on the tickets in the current milestone and submit as PR - this PR💡 Keep in mind, changelogs are for humans, not for machines.
✏️ Remember to add a release diff link at the bottom!
✏️ Handy: use this checklist as the PR description to document the release.
Milestone
Release
mainbranch and copy & paste the changelog to it.✏️ Use the "Auto-generate changelog" button to get GitHub to create a "New contributors" section and the release diff link. Keep those, remove everything else auto-generated and replace it with the manually crafted changelog for humans.
✏️ Check if anything from the link collection at the bottom of the
changelog.mdfile needs to be copied in!Publicize
@Potherca If you have no objection, I will merge this once you've approved it and move forward with the release straight after.