Repository navigation
[TASK] Re-sync with TER 8.6.2 and bump to 8.6.3 - #638
Merged
Merged
Conversation
The tag 8.6.2 already exists on the remote, pointing to an orphaned commit (83ecd85 / 3390ab7, "Refactor ReGenerateDays to resolve serialization issue") that is no longer reachable from any branch but was already tagged before. Renumber the security backport from a34ced3 to 8.6.3 to avoid a version/tag collision. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Version 8.6.2 was tagged/released with a ReGenerateDays scheduler task serialization refactor (constructor injection replaced by GeneralUtility::makeInstance() getters) that caused broader problems and was fully reverted afterwards. Documenting the gap so the orphaned 8.6.2 git tag doesn't cause confusion later. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…package The 8.6.2 tag/commits (83ecd85, 3390ab7) were dropped from this branch's git history at some point (orphaned, unreachable from any branch), but 8.6.2 was already published to TER on 2026-06-10 and is what customers currently have installed. Diffing the actual TER 8.6.2 zip (https://extensions.typo3.org/extension/download/events2/8.6.2/zip) against git turned up exactly two content differences: our new security fix (git ahead) and the ReGenerateDays scheduler task refactor (git behind). Restoring the latter from the released zip: - Classes/Task/ReGenerateDays.php: restore the getter-based refactor (no constructor injection) that fixes "Serialization of 'ReflectionMethod' is not allowed" when the scheduler serializes the task. Verified compatible with this branch's typo3/cms-core ^10.4.36 || ^11.5.23 constraint: both pull doctrine/dbal ~2.13.1, which already ships Doctrine\DBAL\Exception as a forward-compatible interface implemented by DBALException, and TYPO3 core's QueryBuilder provides the executeQuery()/fetchAssociative()/fetchOne() forward-compat wrapper used here. - Documentation/AdministratorManual/Upgrade/Index.rst: restore the "Update to Version 8.6.2" upgrade note (delete + recreate existing scheduler tasks to flush corrupted serialization strings). - Documentation/ChangeLog/Index.rst: restore the original 8.6.2 entry. - Documentation/Settings.cfg: bump to 8.6.3. 8.6.3 now equals TER 8.6.2 plus the RestrictAccessEventListener security hardening, so upgrading from 8.6.2 no longer regresses the scheduler fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
sfroemkenjw
changed the title
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
1 participant
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.
Summary
8.6.2already exists, and - more importantly - 8.6.2 is an officially released, live TER version (uploaded 2026-06-10, containing aReGenerateDaysscheduler task serialization fix). The corresponding git commits (83ecd85e,3390ab75) are orphaned - unreachable from any current branch - so this branch's history silently diverged from what's actually installed by customers.ReGenerateDaysrefactor (git behind, i.e. missing).Classes/Task/ReGenerateDays.php, the "Update to Version 8.6.2" upgrade note, and the original 8.6.2 ChangeLog entry from the released package, so this branch is back in sync with what's actually live on TER.8.6.3(8.6.2is taken) -8.6.3= TER8.6.2+ theRestrictAccessEventListenersecurity hardening (PR [SECURITY] Harden event UID resolution #637). This avoids customers upgrading from 8.6.2 to 8.6.3 silently losing the scheduler serialization fix.ReGenerateDayscode is compatible with this branch'stypo3/cms-core ^10.4.36 || ^11.5.23constraint: both requiredoctrine/dbal ~2.13.1, which already shipsDoctrine\DBAL\Exceptionas a forward-compatible interface implemented byDBALException, and TYPO3 core'sQueryBuilderprovides theexecuteQuery()/fetchAssociative()/fetchOne()forward-compat wrapper used here. Nocompat_versionbranch needed.Test plan
composer validate(PHP 7.4, matching CI)composer ci:php:lint(PHP 7.4) - clean🤖 Generated with Claude Code