Skip to content

Allow gitlib 2 - #1235

Draft
lyrixx wants to merge 2 commits into
phpro:v2.xfrom
lyrixx:gitlib-2
Draft

lyrixx wants to merge 2 commits into
phpro:v2.xfrom
lyrixx:gitlib-2

Conversation

@lyrixx

@lyrixx lyrixx commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

gitlib 2.0 requires PHP 8.4: grumphp requires ^1.7.1 || ^2.0, and keeps 1.7.1, which has the
security fixes of 2.0, on PHP 8.2 and 8.3. Since #1237, the same code runs with both.

The specs no longer double the classes of gitlib, final in 2.0: they run on temporary git
repositories. The raw diff fixture had spaces instead of a tab, which 2.0 refuses.
File::getName() is the new name of a renamed file with both versions, where getNewName() is
nullable in 2.0.

The [DO NOT MERGE] commit installs the main branch of gitlib as 2.0.0 on the highest jobs on
PHP 8.4 and 8.5: drop it once 2.0 is released.

gitlib 2 requires PHP 8.4: grumphp requires ^1.7.1 || ^2.0, and gets
1.7.1, which has the security fixes of 2.0, on PHP 8.2 and 8.3. Since
1.7, the same code runs with both versions.

- The changed files are named by File::getName(), the new name of a
  renamed file with both versions: getNewName() is nullable in gitlib 2.
- The specs no longer double the classes of gitlib, which are final in
  gitlib 2: they run on temporary git repositories instead.
- The raw diff of the specs had spaces instead of a tab, and the status
  of a modification for a new file: gitlib 2 refuses it.
To drop once gitlib 2.0 is released: the highest dependencies on PHP 8.4 and 8.5 then install it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant