Skip to content

feat: Use ramsey/composer-install to use caching of composer dependencies - #762

Merged
nickvergessen merged 1 commit into
masterfrom
feat/add-caching-for-npm-and-composer
Jul 8, 2026
Merged

feat: Use ramsey/composer-install to use caching of composer dependencies#762
nickvergessen merged 1 commit into
masterfrom
feat/add-caching-for-npm-and-composer

Conversation

@DerDreschner

Copy link
Copy Markdown
Contributor

At the moment, we run composer install manually. This means that we have no cache in place and run into 429 Too Many Requests responses sometimes. To avoid that, I would suggest we use ramsey/composer-install in the future, which automatically caches the dependencies. This avoids hitting any rate limits and might improve the overall speed of our CI pipelines.

🤖 AI (if applicable)

  • The content of this PR was partly or fully generated using AI

@DerDreschner
DerDreschner force-pushed the feat/add-caching-for-npm-and-composer branch 3 times, most recently from f575261 to 052f70f Compare July 8, 2026 00:36
…cies

Signed-off-by: David Dreschner <david.dreschner@nextcloud.com>
@DerDreschner
DerDreschner force-pushed the feat/add-caching-for-npm-and-composer branch from 052f70f to df58428 Compare July 8, 2026 00:39
@nickvergessen
nickvergessen merged commit 2f197f0 into master Jul 8, 2026
6 checks passed
@nickvergessen
nickvergessen deleted the feat/add-caching-for-npm-and-composer branch July 8, 2026 06:50
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