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

Unrelated conflict changes (typo3/cms-* vs. mediawiki/semantic-media-wiki) #127

Closed
ohader opened this issue Feb 8, 2024 · 3 comments
Closed
Labels

Comments

@ohader
Copy link

ohader commented Feb 8, 2024

Description

The package typo3/cms-saltedpasswords <0.2.13 suddenly is marked as insecure and blocks the installation the typo3/cms-core package (due to having a replaces declaration for typo3/cms-saltedpasswords: * in typo3/cms-core).

Observation

A bunch of changes were committed recently to roave/security-advisories - where the conflict declaration does not match with the actual original commit in sensiolabs/security-advisories, for instance:

CLI commands used to reproduce the behavior

composer req --dev roave/security-advisories:dev-latest

./composer.json has been created
Running composer update roave/security-advisories
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
  - Locking roave/security-advisories (dev-latest b5487e1)
[...]
composer req typo3/cms-core:^12.4

./composer.json has been updated
Running composer update typo3/cms-core
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.7.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.6.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.5.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.3.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.2.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.1.
    - roave/security-advisories dev-latest conflicts with typo3/cms-core v12.4.0.
    - roave/security-advisories dev-latest conflicts with typo3/cms-saltedpasswords <0.2.13 (typo3/cms-core v12.4.10 replaces typo3/cms-saltedpasswords *).
    - roave/security-advisories dev-latest conflicts with typo3/cms-saltedpasswords <0.2.13 (typo3/cms-core v12.4.9 replaces typo3/cms-saltedpasswords *).
    - roave/security-advisories dev-latest conflicts with typo3/cms-saltedpasswords <0.2.13 (typo3/cms-core v12.4.8 replaces typo3/cms-saltedpasswords *).
    - roave/security-advisories is locked to version dev-latest and an update of this package was not requested.
    - Root composer.json requires typo3/cms-core ^12.4 -> satisfiable by typo3/cms-core[v12.4.0, ..., v12.4.10].
@Ocramius
Copy link
Member

Ocramius commented Feb 8, 2024

@Ocramius
Copy link
Member

Ocramius commented Feb 8, 2024

typo3/cms-core should not replace with a deathstar range there: self.version or something more precise should be used to avoid affected version ranges.

@ohader
Copy link
Author

ohader commented Feb 9, 2024

For the records: A recent change at GitHub "hallucinated" a Composer package, which caused this behavior (side-note: the original advisory was from 2010, Composer was established in 2012 - two years later).
→ GitHub advisory change: github/advisory-database@b403b05

reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82841
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82863
Tested-by: Oliver Klee <[email protected]>
Tested-by: Oliver Hader <[email protected]>
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Oliver Klee <[email protected]>
Reviewed-by: Oliver Hader <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
reviewtypo3org pushed a commit to TYPO3/typo3 that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82873
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/backend that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82841
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/core that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82841
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/info that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82841
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/workspaces that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82841
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/backend that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82863
Tested-by: Oliver Klee <[email protected]>
Tested-by: Oliver Hader <[email protected]>
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Oliver Klee <[email protected]>
Reviewed-by: Oliver Hader <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/core that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82863
Tested-by: Oliver Klee <[email protected]>
Tested-by: Oliver Hader <[email protected]>
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Oliver Klee <[email protected]>
Reviewed-by: Oliver Hader <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/info that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82863
Tested-by: Oliver Klee <[email protected]>
Tested-by: Oliver Hader <[email protected]>
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Oliver Klee <[email protected]>
Reviewed-by: Oliver Hader <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/workspaces that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82863
Tested-by: Oliver Klee <[email protected]>
Tested-by: Oliver Hader <[email protected]>
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Oliver Klee <[email protected]>
Reviewed-by: Oliver Hader <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/backend that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/core that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/info that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/workspaces that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/backend that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82873
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/core that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82873
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/info that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82873
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
TYPO3IncTeam pushed a commit to TYPO3-CMS/workspaces that referenced this issue Feb 9, 2024
The so called "death star" range for replacements has to be
used with caution [1] as it replaces all versions of the
replaced packages, including old or insecure versions.

That effectively means the replacing package marks itself as matching
in queries for insecure versions, once a security advisory[2]
is submitted for the replaced packages.

The extension replacements are now adapted to use the more precise
self.version qualifier to avoid matching named security advisories as
suggested by:
Roave/SecurityAdvisories#127 (comment)

[1] https://getcomposer.org/doc/04-schema.md#replace
[2] GHSA-cgr9-h9qq-x9fx

Resolves: #103082
Releases: main, 13.0, 12.4, 11.5
Change-Id: I6353df15d6cbf039bab60644a103669495b26605
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82873
Tested-by: core-ci <[email protected]>
Tested-by: Benjamin Franzke <[email protected]>
Reviewed-by: Benjamin Franzke <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants