NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #3194 most downloaded on Packagist
Centralized dev-dependencies, configs, and CI tooling for Netresearch TYPO3 extensions
Latest stable
v2.1.0
Last release 12 days ago
10 Nov 2026
Release timing varies
gaps range from 2 weeks to 3 months
Nearly every release is documented
notes for 33 of 34 stable releases
Nothing withdrawn
no release was ever pulled
8 months old
34 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
A minor release: the PHPat layer rules and a TypedArray test helper ship with the package, a phplint check for a project's template copy, opt-in compa
A minor release: the PHPat layer rules and a TypedArray test helper ship with the package, a phplint check for a project's template copy, opt-in compact CI, a Crowdin integration through signed pull requests, and runTests.sh working inside git worktrees (all by @CybotTM).
Added
TypedArray test helper are part of the package (#310).bin/check-phplint-config checks a project's copy of the phplint template (#309).Fixed
runTests.sh mounts a worktree's git directory into its containers. In a git worktree .git points outside the extension, so git failed in every container, a changelog check reported existing tags as missing, and composer install without CAPTAINHOOK_DISABLE stopped with invalid .git path (#333).Dependencies
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
A patch release that makes a failed e2e frontend check name its cause in the job log (#307 by @CybotTM).
A patch release that makes a failed e2e frontend check name its cause in the job log (#307 by @CybotTM).
E2E_LOG_LINES (default 60) lines of the Apache and PHP-FPM container logs and of every TYPO3 log file in var/log before it stops the setup. Before, the job log held only the last status, and the instance directory with the logs is discarded by a CI runner.e2e_require_frontend. Self-CI drives it with a stand-in container binary: a frontend answering 200 passes and prints no logs, one answering 500 fails and prints both container logs and the TYPO3 log.A patch release that stops e2e provisioning from failing on a brief name-lookup failure in the podman network (#306 by @CybotTM).
A patch release that stops e2e provisioning from failing on a brief name-lookup failure in the podman network (#306 by @CybotTM).
/typo3/login before it hands over to the suite. That check, added in 2.0.0, failed the setup whenever PHP-FPM or the database host was briefly unresolvable on GitHub's runners, although the suite itself survives that. Extensions whose E2E job stopped with "e2e: the backend login page answered 500, not 200." pass again.E2E_PROBE_ATTEMPTS, E2E_PROBE_DELAY), instead of once, and prints one line per failed attempt. A page that keeps failing still stops the setup.Build/Scripts/check-e2e-provision-probe.sh, which drives the probe with a stand-in container binary.A patch release that makes the shared PHP-CS-Fixer rules collapse runs of blank lines again (#305 by @CybotTM).
A patch release that makes the shared PHP-CS-Fixer rules collapse runs of blank lines again (#305 by @CybotTM).
no_extra_blank_lines carries the token list of @Symfony again (attribute, case, continue, curly_brace_block, default, extra, parenthesis_brace_block, square_brace_block, switch, throw, use). @PER-CS3x0 comes after @Symfony in the shared rules and set the rule to the use token only, so runs of blank lines were collapsed only between imports. Extensions that pass their own no_extra_blank_lines rule only to restore this can drop it.Build/Scripts/check-cgl-blank-lines.php, which applies the shared rules to a probe method with three blank lines in a row. It and check-cgl-import-order.php share one probe runner, Build/Scripts/cgl-probe.php.Extensions with runs of blank lines inside methods or other blocks get them collapsed on the first fixer run with this release.
A patch release that fixes the import order of the shared PHP-CS-Fixer rules (#304 by @CybotTM).
A patch release that fixes the import order of the shared PHP-CS-Fixer rules (#304 by @CybotTM).
ordered_imports keeps the group order of @PSR12 and @PER-CS3x0 again: class imports first, then use function, then use const, each group sorted alphabetically. The shared override set only sort_algorithm, which dropped imports_order, so function and constant imports were sorted in between the class imports. Extensions that pass their own ordered_imports rule only to restore the grouping can drop it.Build/Scripts/check-cgl-import-order.php, which applies the shared rules to a probe file and compares the resulting import block.Extensions with use function or use const imports get their import blocks regrouped on the first fixer run with this release.
The package requires phpat/phpat 0.12.4 or later, the first version with shouldNot(). 0.12.4 deprecates the older shouldNotX() methods, which the shar…
A patch release with four fixes that the first extension migration to 2.0 ran into (#303 by @CybotTM).
trailing_comma_in_multiline carries the @PER-CS3x0 configuration again. The shared override had narrowed it to arrays, arguments and parameters; it now also covers match, array destructuring and after_heredoc. The override stays, because @PHP8x2Migration would otherwise reset the rule to arrays only.TypedPropertyFromCreateMockAssignRector. In a test case the rule replaced an existing class type such as private Foo $foo with plain MockObject, so passing the property where a Foo is expected no longer type-checked. Intersection types (Foo&MockObject) were not affected.phpat/phpat 0.12.4 or later, the first version with shouldNot(). 0.12.4 deprecates the older shouldNotX() methods, which the shared PHPStan config reports.^2.0, and states that the Build/ paths for tool configs are examples.Rector: the deprecated EARLY_RETURN and INSTANCEOF sets are gone; from Rector 2.6.5 they register no rules (#293). The factory takes a third argument…
A major release: three reusable workflows change behaviour that callers rely on, and the Composer package raises three tool floors. Consumers move with "netresearch/typo3-ci-workflows": "^2.0" in require-dev.
security.yml fails Opengrep on ERROR findings as well as WARNING. The old default --severity WARNING selected that one level, so ERROR findings were neither reported nor failing the job (#269). The Opengrep rule set behind --config auto is now pinned (#302), and a misfiring registry rule is replaced (#292).license-check.yml refuses the SPDX ids SSPL-1.0 and BUSL-1.1; the old pattern matched only the bare strings "SSPL" and "BSL" (#269).release-typo3-extension.yml creates the GitHub release right after the build, before TER, Packagist and docs.typo3.org. A failed target no longer withholds the release; the release body carries a publication status section that a final job fills in (#270).rector/rector ^2.6.5, overtrue/phplint ^9.6.2 and captainhook/hook-installer ^1.0.5 (#293, #296, #299).These follow the request of @magicsunday in #285 to let extensions drop their per-repository strict layer.
Rector: the deprecated EARLY_RETURN and INSTANCEOF sets are gone; from Rector 2.6.5 they register no rules (#293). The factory takes a third argument with the options tests, php and typo3; typo3: 14 also skips the plugin migration rule that writes an empty upgrade wizard (#297).
PHP-CS-Fixer: the factory excludes .Build, .build, .ddev, .pnpm-store, config, node_modules, public and var by name, so the result does not change when PHP-CS-Fixer 4 stops skipping dot directories, and takes a fourth argument with more excludes (#294).
PHPStan: phpstan.neon and the Rector-only phpstan-rector.neon share one base file instead of duplicating five parameters (#295). The README lists what the shared config turns on beyond the usual tool list (#300).
Templates: config/phpunit/ holds PHPUnit configurations for unit and functional tests, valid from PHPUnit 10.1 to 13, and the Composer bin check-phpunit-config asserts their strictness flags in a baseline or a --strict profile (#298). config/editorconfig/.editorconfig and config/phplint/.phplint.yml are templates for the files every extension keeps (#299).
The README documents the CaptainHook plugin's configuration path and how to switch it off (#296).
ci.yml: an opt-in cell at the lower bound of the dependencies (#259); a committed composer.lock is kept and updated only where it cannot serve the matrix cell (#265); the acceptance tier collects and uploads coverage, reported by @magicsunday in #249 (#250).
E2E: the database images come from ghcr.io/netresearch/ci-mirror (#286, #287, after the ECR mirror in #277); the PHP server runs without the OPcache JIT and records how it ends (#263); the backend must be ready before the suite (#256); typo3-setup-extensions reaches the environment (#271).
The runner removes its network on every exit (#276).
Release: a reusable gate on required workflows (#247); a tag that contradicts composer.json's TYPO3 version is refused (#260); every gh call names the repository (#253); release-asset uploads survive GitHub's flaky endpoint (#252); a docs render is confirmed and never fails a release (#254).
TER: callers can replace tailor's packaging exclude list (#245); the upload comment is checked before publishing, and level-1 CHANGELOG headings are read (#275).
Also: 14 SonarCloud findings on main resolved (#261), an SPDX notice on the runTests bootstrap stub (#266), and dependency updates.
Three custom PHP-CS-Fixer rules, all registered by the shared config factory and none of them enabled.
Three custom PHP-CS-Fixer rules, all registered by the shared config factory and none of them enabled.
Line breaking and blank lines are the two things no shipped fixer does, and both stop being invisible the moment code is written back from a syntax tree rather than typed: a printer reproduces whatever the rules say, so every decision no rule describes is lost on the first pass.
Netresearch/break_long_method_chain (#238) puts every call of a chain on its own line from minimum_links calls on, default 3. Nothing among php-cs-fixer's 303 fixers has a line-width concept and method_chaining_indentation only indents a chain somebody already broke, so a chain written on one line stays on one line however long it grows.
Netresearch/blank_line_after_control_structure (#239) separates a control structure from the statement after it. blank_line_before_statement writes in front of a statement; nothing writes after a block. Measured over a 48-class extension, that is the rule the code keeps most consistently — a closing brace inside a method body is followed by a blank line in 232 of 247 places, 93 %, against 37 % for the blank line before an if that the shipped rule does enforce.
Netresearch/blank_line_before_comment (#241) separates a comment on a line of its own from the code above it — 274 of 309 places, 89 %. Inside an array or an argument list the rule is off, which is where all the counter-examples sit.
All three are registered but not enabled: reflowing a code base is a decision each project makes in a commit of its own, not something that arrives with a dependency update. The config factory takes a third argument for project rules, and the README's Code Style section documents each rule and shows how to switch one on.
Also in this release: the chain fixer leaves indentation to statement_indentation rather than writing and comparing it, which is what kept a chain nested in another chain's argument from ever settling (#242); its indent walk now runs only for a chain that is going to break. The Rector cap lifted after typo3-rector 3.15.1 shipped the container fix (#236), and the usual dependency updates (#228, #231, #232, #233, #234, #235, #240) from @renovate.
Two fixes, both about a job that never starts.
Two fixes, both about a job that never starts.
rector/rector 2.6.4, published 2026-08-27, removed RectorConfig::bind(). ssch/typo3-rector still calls that method in its own config/config.php and admits the release through its ^2.5.2 constraint, so every consuming extension lost its Rector job the moment CI re-resolved: Call to undefined method Rector\Config\RectorConfig::bind(), raised while Rector boots, before a single file is analysed. No consumer pins Rector and none ships a composer.lock, so the break arrived without a change of their own — reproduced on an unmodified checkout of netresearch/t3x-nr-vault's main, observed the same day in netresearch/t3x-nr-llm.
The constraint is now ^2.0 <2.6.4. It is temporary and goes once typo3-rector ships a release that no longer calls bind(); the incompatibility is tracked upstream at https://github.com/sabbelasichon/typo3-rector/issues/4922. Thanks @CybotTM.
"Smoke test rector config factory" asserted that config/rector/rector.php returns a callable. It still does under 2.6.4 — the breakage sits one layer further in, at container build — so this repository stayed green through a release that took down every consumer.
The added step runs Rector against a throwaway extension fixture with a TYPO3 set applied, because that set is what pulls typo3-rector's own config into the run; without one the boot never reaches the code that broke. Exit 2 passes, since a dry run finding changes in the fixture is not a boot failure, but anything other than 0 or 2 fails, so a missing binary cannot report OK. Measured in both directions before shipping: exit 1 on the bind() error under 2.6.4, green under 2.6.3.
fuzz.yml's "Install dependencies" ran a plain composer install, unlike every job in ci.yml, which first runs composer config --no-plugins audit.block-insecure false. On a maintenance branch pinned to an EOL TYPO3 minor, every publicly installable core version can carry an advisory whose real fix ships only via ELTS and never reaches public Packagist. Composer's solver then refuses to resolve at all — a hard failure, not a warning — and no version bump gets a caller out of it.
Confirmed against netresearch/t3x-nr-image-optimize's TYPO3_12 branch, where fuzz / Fuzz Tests failed on "Your requirements could not be resolved to an installable set of packages" while the same branch's ci job installed the identical typo3/cms-core ^12.0 constraint. Both "Install dependencies" steps in the file are fixed, fuzz-tests and mutation-testing. security.yml's audit job is untouched and still reports the same advisories. Thanks @aseemann.
Four runner fixes, all of the same class: a green result standing in for a run that never happened.
Four runner fixes, all of the same class: a green result standing in for a run that never happened.
A fractor suite (#218, #223, @CybotTM).
Fractor is rector's sibling for the file types rector does not read -- TypoScript, Fluid, YAML, TCA. Six extensions on this runner carry a fractor script and had to leave the shell for half their upgrade tooling. -s fractor writes, -s fractor -n checks, exactly like cgl and rector. The standard config location mirrors rector's (Build/fractor/fractor.php); a flat Build/fractor.php is found and reported as non-standard.
The check does not trust fractor's exit code, because that code lies: fractor process --dry-run exits 0 while reporting "[OK] 46 files would have been changed", where rector exits 2. --output-format=json is worse -- on the same invocation it reports "changed_files": 0 against the console's 46. The check therefore parses the console line, which is the only signal that tells the truth. A repository with pending fractor changes now fails -s fractor -n instead of passing.
An honest lint (#217, #223, @CybotTM).
-s lint ran find Classes Configuration Tests .... A repository missing one of those directories got a find error on stderr, a discarded exit status, and a green suite that had opened two paths out of three -- and root-level PHP (ext_localconf.php, ext_tables.php, ext_emconf.php, Build/*.php) was never opened at all, though a syntax error in ext_localconf.php takes down the whole installation. Measured by breaking ext_localconf.php on purpose: the old runner said SUCCESS, exit 0.
The suite now lints everything the repository ships and prunes what it generates (.git, vendor, .Build, .build, node_modules, var, public, Documentation-GENERATED-temp), and prints the file count -- a lint that says nothing is indistinguishable from a lint that looked at nothing.
-s integration runs its own config, or refuses (#212, #224, @CybotTM).
The suite selected a testsuite NAME inside the already-detected unit config; an extension keeping its integration tests in a config of their own got the unit suite re-run under an integration banner. On t3x-cowriter that was 614 green unit tests standing in for five integration classes that had never run; with the config detected (Build/phpunit/IntegrationTests.xml and friends) the same call runs the 30 integration tests. Where neither a config nor an "integration" testsuite exists, the suite now refuses with the searched paths listed instead of green-running the wrong file.
Tool arguments pass through (#211, #224, @CybotTM).
The reusable workflow appends arguments to the composer scripts (composer ci:test:php:unit -- --coverage-clover=...), and composer strips its own -- before invoking the script -- so the runner received the bare form and died on "illegal option". Six checks failed on t3x-nr-passkeys-fe this way while every local call passed. The runner has only short options, so an argument starting with -- can never be its own: everything from an explicit -- or the first --long argument on now reaches the tool. A mistyped short option still fails loudly. For the extensions that branched around this in their composer scripts (t3x-nr-llm, t3x-nr-passkeys-fe), the LOCAL half of those scripts now accepts appended tool arguments; the branching itself stays — its CI half selects the matrix cell's host PHP, which the runner's own containers would override (#189 tracks the mode that would retire it).
Every consumer on a ^1.x constraint receives this on its next composer update; no manifest change is needed. All four fixes carry cases in check-runner-detection.sh that were seen to fail against the unpatched runner before being accepted.
The e2e instance's TYPO3 version no longer drags in -t (#222, @CybotTM).
The e2e instance's TYPO3 version no longer drags in -t (#222, @CybotTM).
e2e-provision.sh read the major from TYPO3_VERSION, which is only set by -t. That flag is not suite-gated: it also rewrites the extension's own composer.json and runs a full composer require typo3/cms-core:<constraint> before the suite starts. For an e2e run the require does nothing -- the instance is installed separately, from scratch -- and a resolve that fails there kills the job before provisioning even begins, leaving a narrowed composer.json behind in the checkout.
E2E_TYPO3_VERSION from the environment now wins, then TYPO3_VERSION, then 13. The first is what the reusable e2e workflow already passes to a scripted consumer, as a constraint like "^14.3", so a CI wrapper can select the instance's version without touching the manifest at all. A constraint is reduced to its major; anything unparseable falls through to 13 rather than being guessed at.
Only v1.10.0 is affected, and only a consumer that uses the provisioning introduced there. -t itself is unchanged: it still narrows composer.json for unit and functional, which is what those suites want.
-s e2e can build the TYPO3 it tests (#220, @CybotTM).
-s e2e can build the TYPO3 it tests (#220, @CybotTM).
Until now the suite needed an address: an already-running instance named by TYPO3_BASE_URL, by e2e_target() or by E2E_BASE_URL. The half that BUILDS such an instance lived in one extension's 1775-line e2e.sh, which is why t3x-rte_ckeditor_image was the only repository in the fleet with e2e at all.
assets/Build/Scripts/e2e-provision.sh is that half with nothing extension-specific in it: MariaDB, a composer-installed TYPO3, the site configuration and root template, PHP-FPM, Apache, and a check after each that it actually came up. It is sourced as a sibling of runTests.sh.
Four optional hooks in runTests.conf carry what is specific to an extension -- e2e_provision_packages, e2e_provision_typoscript, e2e_provision_site_dependencies and e2e_provision_seed. Defining any of them opts a repository in. An extension that only points at a running instance is untouched, and one that defines none is unaffected by this release.
Putting a real extension through that path found four gaps in the existing suite, all fixed here:
npm ci refuses without a lockfile, so a consumer that gitignores it got EUSAGE and no tests. It falls back to npm install --no-save and says that the Playwright version is then not pinned against the browser image.
E2E_TEST_DIR names the directory holding the suite's package.json, lockfile and Playwright config when it is not the repository root. Both the container working directory and the lockfile probe that selects the Playwright image follow it, so a suite in Tests/E2E resolves its own version instead of the fallback pin.
The Playwright container now also receives BASE_URL (what a Playwright config conventionally reads; TYPO3_BASE_URL remains the contract), TYPO3_BACKEND_PASSWORD, E2E_VARIANT and the effective TYPO3 major. Without the password every backend test fails at login, and when the run created the instance the password is known nowhere else.
wait_for takes an optional third argument, the timeout in seconds, default 10 as before. A MariaDB container initialising its data directory needs more.
The frontend check asserts the status code instead of printing it. A 403 used to scroll past, and the suite then reported a page of assertion failures for an instance that was never serving.
Verified by running t3x-rte_ckeditor_image's suite through the new path: 214 tests, 204 passed, 10 skipped, exit 0 -- the same result its own script produces. Both abort paths were exercised by injecting the defect rather than by reading the code: a nonexistent composer package and an unreachable frontend each stop the run with the cause named, and neither reaches Playwright.
Coverage runs are no longer silently empty (#216, #209, @CybotTM).
A PHPUnit config carrying <coverage><report> makes coverage mandatory, but the suites passed -dxdebug.mode=off, so such a run ended at "No tests executed!". Both settings have to agree: Xdebug 3 lets the XDEBUG_MODE environment variable win over the ini flag, so setting only the flag changed nothing. The demand is now read from the config. Three extensions were blocked from migrating by this.
A repository whose PHPUnit config gains a <report> block will see its runs get slower without asking, and the runner says so on each affected call.
Scripted e2e consumers are told about COMPOSER_RETRY (#219, @CybotTM).
Passing setup-script replaces the default pipeline, and with it the only step that applied composer_retry. The helper was exported all along but absent from the input's documented environment list, so every scripted consumer ran Composer unprotected -- and Composer has no git fallback for a failed dist download, so one HTTP 504 from api.github.com ends the job. Two e2e matrices in t3x-rte_ckeditor_image were ejected from its merge queue that way within three days, on two unrelated pull requests.
Also in this release: a conf can take its own e2e environment down again with e2e_teardown (#215), and the CodeQL action moved to v4.37.8 (#221).
Consumers referencing the reusable workflows with @main are unaffected by the runner changes; those ship in the Composer payload and reach an extension when it updates the package.
This repository releases itself (#210, #213).
This repository releases itself (#210, #213).
Ten tags between v1.4.0 and v1.8.2 carried no Release object, so releases/latest answered v1.3.4 from 2026-08-04. The cause was not a withheld decision: every workflow here that mentions tags: is a workflow_call reusable for consumers, and the only push trigger was self-ci on branches. release.yml is a path this repository offers, not one it took.
self-release.yml now fires on a signed tag push and runs the same chain the skill repos run: verify the tag is annotated and signed, build, checksum, Cosign sign-blob, SLSA attest, publish -- all in one job before the assets become public, so no window exists in which unattested artefacts are downloadable. The release notes are the annotated tag message, read with %(contents:body) so the SSH signature block stays out of them. The release is created with gh release create, not a third-party action.
The README gained a "Releasing This Repository" section, because the release path being knowledge nobody had written down is part of how the gap survived ten tags.
Read this before assuming the archives changed: they did not. git archive applies .gitattributes, whose export-ignore strips .github/, docs/, scripts/ and README.md -- and this release touches nothing else. The Composer payload in typo3-ci-workflows-v1.9.0.tar.gz is byte-identical to the one v1.8.2 would have produced, verified by extracting both and diffing.
That is deliberate rather than an oversight. The archive is the half worth attesting: uses: ...@main is resolved by GitHub from the git ref and never downloaded, while the runner IS installed, so a consumer can now check the copy in their .Build/vendor/netresearch/typo3-ci-workflows/ against a signed checksum. What this tag ships is the release path itself, and the first run of it.
Consumers referencing the workflows with @main are unaffected. Nothing about what a workflow does has changed -- only what a tag produces.
fix(runner): find a functional config at Build/phpunit.functional.xml by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/208
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.8.1...v1.8.2
fix(fuzz): select the suite that was detected, not the one that was configured by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/2
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.8.0...v1.8.1
fix(ci): fail a test job that has nothing to run, instead of reporting success by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/1
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.7.2...v1.8.0
fix(runtests): read the conf before deriving from it, and shard the same suite the serial run does by @CybotTM in https://github.com/netresearch/typo3
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.7.1...v1.7.2
fix(runtests): restore the values v1.7.0 dropped, and guard the class by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/184
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.7.0...v1.7.1
feat(runtests): find what the extension already declares by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/183
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.6.0...v1.7.0
feat(runtests): the suites the remaining forks still need by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/182
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.5.1...v1.6.0
fix(runtests): stop asking for what the extension already declares by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/181
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.5.0...v1.5.1
fix(ci): run test jobs with zend.assertions=1 by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/159
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.4.0...v1.5.0
fix(deps): unpin the analysis toolchain by @CybotTM in https://github.com/netresearch/typo3-ci-workflows/pull/158
Full Changelog: https://github.com/netresearch/typo3-ci-workflows/compare/v1.3.4...v1.4.0
Two changes, both consequences of the 2026-08-03 fleet breakage. First, the shared PHPStan configs no longer hardcode the .Build vendor dir: bootstrap
Two changes, both consequences of the 2026-08-03 fleet breakage. First, the shared PHPStan configs no longer hardcode the .Build vendor dir: bootstrapFiles resolve relative to the declaring config file, the no-extension-installer includes traverse to the vendor root relative to their own location, and excludePaths list both vendor-dir spellings — repos using .build (t3x-universal-messenger, t3x-nr-image-optimize, t3x-nr-textdb) can now adopt the shared configs. Second, rector/rector (2.6.1) and ssch/typo3-rector (3.14.4) are pinned to exact versions: Rector activates PHPUnit rules from the resolved phpunit version, so with caret constraints every consumer's Rector job changed behavior whenever upstream tagged a release. Tool upgrades now arrive as Renovate PRs in this repository, pass its CI, and reach consumers through a tagged release. See #154.
Rector 2.6.0 (released 2026-08-03) removed the deprecated SetList::STRICT_BOOLEANS. The shared config/rector/rector.php still listed it, so the Rector…
Rector 2.6.0 (released 2026-08-03) removed the deprecated SetList::STRICT_BOOLEANS. The shared config/rector/rector.php still listed it, so the Rector job in every consuming extension failed with "Undefined constant Rector\Set\ValueObject\SetList::STRICT_BOOLEANS" as soon as a CI run resolved the new Rector release. The set is dropped without replacement: Rector's own deprecation points at the code-quality and coding-style sets, both of which the shared config already loads. See #151.
v1.3.0/v1.3.1 introduced ergebnis/phpstan-rules and a curated parameters: ergebnis: { allRules: false, … } block in the shared config/phpstan/phpstan.
v1.3.0/v1.3.1 introduced ergebnis/phpstan-rules and a curated parameters: ergebnis: { allRules: false, … } block in the shared config/phpstan/phpstan.neon. The block is correct for the regular PHPStan job (extension-installer registers ergebnis there), but Rector's bundled phpstan.phar does not have ergebnis registered — so every downstream extension's Build/rector.php (which requires the shared config/rector/rector.php, which set phpstanConfig to the project's Build/phpstan.neon, which includes the shared neon) tripped:
PHP Fatal error: Uncaught _PHPStan_xxx\Nette\Schema\ValidationException:
Unexpected item 'parameters › ergebnis'.
ci / Rector went red on every t3x-* extension after v1.3.0 landed.
config/phpstan/phpstan-rector.neon ships with the package — same level / treatPhpDocTypesAsCertain / inferPrivatePropertyTypeFromConstructor / excludePaths / bootstrapFiles as the regular shared neon, but no ergebnis include.config/rector/rector.php now points $rectorConfig->phpstanConfig() at the new file by default, replacing the previous $projectRoot . '/Build/phpstan.neon' path.Pick up with composer update. The ^1.0 / ^1.1 / ^1.2 / ^1.3 caret ranges all select v1.3.2 automatically. Downstream Build/rector.php works unchanged.
The temporary in-repo Build/phpstan-rector.neon + setParameter(PHPSTAN_FOR_RECTOR_PATHS, ...) workaround landed in netresearch/t3x-rte_ckeditor_image#793 is no longer needed once composer update picks up v1.3.2. A sweep of the affected repos to revert it is on the way.
End-to-end on rte_ckeditor_image: vendor/bin/rector process --config Build/rector.php runs to completion without the ValidationException.
v1.3.0 re-added ergebnis/phpstan-rules (which had been dropped in v1.2.0). Because the package auto-registers via phpstan/extension-installer with erg
v1.3.0 re-added ergebnis/phpstan-rules (which had been dropped in v1.2.0). Because the package auto-registers via phpstan/extension-installer with ergebnis.allRules: true by default, every consumer extension's PHPStan matrix turned red within minutes — the rules forbid extending ActionController / AbstractEntity, named arguments on TYPO3 core APIs, isset(), switch, nullable parameters, and parameters with null default values (all standard TYPO3 patterns).
Shared config/phpstan/phpstan.neon now sets ergebnis.allRules: false and opts in to the six rules that align with TYPO3 coding standards:
declareStrictTypes — required by TYPO3 coding standardsnoCompact — obscure, readable alternatives existnoErrorSuppression — @-suppression hides bugsnoEval — securitynoReturnByReference — obscuretestCaseWithSuffix — naming conventionAll other ergebnis rules are disabled and can be re-enabled per-extension with ergebnis.<rule>.enabled: true.
No action required — pick up with composer update. The ^1.2 / ^1.3 caret ranges select v1.3.1 automatically.
Applied to t3x-nr-llm:
The reusable ci.yml workflow's coverage-tool input flipped its default from pcov to xdebug. Consumers that set coverage-tool explicitly are unaffected
coverage-tool now defaults to xdebugThe reusable ci.yml workflow's coverage-tool input flipped its default from pcov to xdebug. Consumers that set coverage-tool explicitly are unaffected.
ci:test:php:unit:coverage etc.) set XDEBUG_MODE=coverage locally. With CI on pcov, consumers periodically saw tests that passed locally and went red in CI for coverage-tool-specific reasons, especially around PHPUnit's beStrictAboutCoverageMetadata=\"true\". Observed concretely in netresearch/t3x-nr-image-optimize#91/#93.--coverage-html become more useful with xdebug data.Consumers with large matrices where coverage runtime dominates can still explicitly select pcov:
```yaml jobs: ci: uses: netresearch/typo3-ci-workflows/.github/workflows/ci.yml@v1.3.0 with: upload-coverage: true coverage-tool: 'pcov' # opt in to the line-only speedup ```
The inline description on the input now documents the tradeoff so future consumers see it on hover in VS Code / gh workflow view.
No action required for 99% of consumers — CI runtime goes up by a few minutes, diagnostics improve. If your matrix is very large (20+ jobs) and coverage runtime dominates, pin coverage-tool: 'pcov' explicitly.
The main branch has accumulated several non-breaking additions since v1.1.3 was tagged 2026-03-28:
release-typo3-extension.yml orchestrator (#66) — Phase 1 of a centralized TYPO3 extension release orchestratort3docs-ci-deploy run instead of fetching the rendered URL (more reliable)actions/download-artifact v8, shivammathur/setup-php, softprops/action-gh-releaseA signed v1.2.0 tag exists on the repository (2026-03-16) but was never published as a GitHub Release. It points at a pre-orchestrator commit and is effectively dead weight. Consumers pinning to @v1.2.0 would have received behaviour closer to v1.1.3 than to v1.3.0; migrating them to @v1.3.0 is recommended.
Nothing published for this version
fix(ci): remove matrix vars from job names
Revert `stubFiles` to `bootstrapFiles` with `class_exists` guard: stubFiles only provides type info — PHPStan's attribute resolver needs the class to
stubFiles to bootstrapFiles with class_exists guard: stubFiles only provides type info — PHPStan's attribute resolver needs the class to actually exist at runtime. Reverted to bootstrapFiles which executes the PHP file, but added a class_exists(::class, false) guard to prevent "Cannot redeclare class" fatal on PHPUnit 12+ where the real class is provided by phpunit/phpunit. This was causing PHPStan failures on PHP 8.2 with TYPO3 ^13.4.21 in CI.> Superseded by [v1.1.2](https://github.com/netresearch/typo3-ci-workflows/releases/tag/v1.1.2) — v1.1.1 changed bootstrapFiles to stubFiles, but stub
Superseded by v1.1.2 — v1.1.1 changed
bootstrapFilestostubFiles, butstubFilesdoesn't work for attributes (PHPStan needs the class to exist at runtime). v1.1.2 reverts tobootstrapFileswith aclass_existsguard.
paths from shared PHPStan config: PHPStan NEON includes MERGE indexed arrays — having default paths would force all extensions to analyze Classes/, Configuration/, Tests/ even if they define their own (the lists concatenate, not replace). Each extension must define its own paths.stubFiles instead of bootstrapFiles: bootstrapFiles which executes the PHP file.stubFiles doesn't work for attributes.phpVersion(80200) inside if ($projectRoot) block: Preserves true v1.0 backward compatibility.paths() REPLACES (not additive like sets()/skip())./data/links.json so they can be updated easily.TYPO3 upgrade wizard deprecation ignoreErrors (attribute.deprecated, implementsDeprecatedInterface, classConstant.deprecatedClass)
Superseded by v1.1.1 — v1.1.0 had issues: PHPStan paths merged instead of overriding (removed from shared config in v1.1.1),
bootstrapFilescaused fatal on PHPUnit 12 (changed tostubFiles),phpVersion(80200)was unconditional (moved inside$projectRootblock). Extensions MUST keep their ownpathsin phpstan.neon.
Centralize more configuration into shared configs, reducing extension boilerplate from ~150 lines to ~30 lines.
config/phpstan/phpstan.neon)paths (Classes/, Configuration/, Tests/) — extensions override if they have additional pathsexcludePaths (.Build/*, ext_emconf.php)bootstrapFilesstubFiles (fixed in v1.1.1)ignoreErrors (Unit: offsetAccess, argument.type; Functional: cast.int, mixed types)ignoreErrors (attribute.deprecated, implementsDeprecatedInterface, classConstant.deprecatedClass)reportUnmatched: false for safety across varying extension structuresconfig/rector/rector.php)$projectRoot parameter (backward compatible — default '' preserves v1.0 behavior)STRICT_BOOLEANS and UP_TO_PHP_82 to shared setsconfig/php-cs-fixer/config.php)$createConfig($header, $projectRoot) returns ready-to-use PhpCsFixer\ConfigSee v1.1.1 release notes for corrected migration guidance.
Adds a Composer library package (netresearch/typo3-ci-workflows) providing shared dev-dependencies and configs for Netresearch TYPO3 extensions.
Adds a Composer library package (netresearch/typo3-ci-workflows) providing shared dev-dependencies and configs for Netresearch TYPO3 extensions.
| File | Purpose |
|---|---|
composer.json |
17 shared dev-dependencies (PHPStan, PHP-CS-Fixer, Rector, testing-framework, CaptainHook, etc.) |
config/phpstan/phpstan.neon |
Shared PHPStan parameters (level 10, strict) |
config/php-cs-fixer/rules.php |
Shared ruleset (@Symfony + @PER-CS3x0 + @PHP8x2Migration) |
config/rector/rector.php |
Shared Rector base config (code-quality, dead-code, etc.) |
config/captainhook/captainhook.json |
Pre-commit hooks (lint, CGL, PHPStan) |
Makefile.include |
Standard Make targets (quality, test, ci, clean) |
{
"require-dev": {
"netresearch/typo3-ci-workflows": "^1.0"
}
}
Extensions can then reference shared configs and override as needed. See PR #2 for full details.