Skip to content

Fix issues with lfs and composer auth#41

Open
chippison wants to merge 2 commits into
mainfrom
fix-issues-with-lfs-and-composer-auth
Open

Fix issues with lfs and composer auth#41
chippison wants to merge 2 commits into
mainfrom
fix-issues-with-lfs-and-composer-auth

Conversation

@chippison

@chippison chippison commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Description

Issue 1:

We initially had an issue with lfs failing because we were pulling all our screenshot LFS for every job we did. This made us encounter our LFS limit.

We have added a fix in core so that we only pull the plugin's LFS screenshot on the job its doing it on. We just want premium plugins to get this fix as well.

Issue 2

We also have an issue where our 8.2 and 8.5 System and Integration tests failing. This was actually caused by compose

Root cause

For PHP 8.x, scripts/bash/prepare.sh bumps phpunit via
composer remove --dev phpunit/phpunit then
composer require --dev phpunit/phpunit ~9.3 ....
The require re-resolves the tree, which makes composer fetch commit
metadata for dev-master-pinned deps (e.g. matomo-org/matomo-coding-standards)
from api.github.com. Those requests were unauthenticated, so GitHub
returned an HTTP 429 anti-scraping throttle:

We have made the fix here to add in our github token when we do composer require.

Checklist

  • [✔] I have understood, reviewed, and tested all AI outputs before use
  • [✔] All AI instructions respect security, IP, and privacy rules

Review

Comment thread scripts/bash/prepare.sh
# Plugin builds only compare the plugin's own screenshots, so skip Matomo
# core's screenshots (~124MB) and scope the plugin's pull to its UI dir.
cd $WORKSPACE/matomo/plugins/$PLUGIN_NAME
git lfs pull --include="tests/UI/expected-screenshots/*" --exclude=

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some plugins might also use "tests/UI/expected-ui-screenshots/*"

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.

2 participants