Skip to content

ci: open an issue when a framework ships a major the store lacks - #108

Merged
geodro merged 1 commit into
mainfrom
ci/upstream-majors
Nov 16, 2026
Merged

geodro merged 1 commit into
mainfrom
ci/upstream-majors

Conversation

@geodro

@geodro geodro commented Nov 16, 2026

Copy link
Copy Markdown
Member

Nobody watches upstream for new framework majors, so a release like Laravel 14 could go a while without a definition here. Every Monday this workflow looks up each framework's composer package on Packagist and compares the newest stable major with the latest in index.json. A newer one becomes an issue that says which file to add, and a title that already exists, open or closed, is never opened again. Bedrock, WordPress and Testbench are looked up by their Packagist names since they are detected by files, and Magento, ExpressionEngine and Joomla are not on Packagist, so the job summary lists them to check by hand.

Every Monday the workflow looks up each framework's composer package on Packagist and compares the newest stable major with the index's latest. A newer one becomes an issue titled after the framework and version, and a title that already exists, open or closed, is never opened again. Frameworks that are not on Packagist are listed in the job summary so they can be checked by hand.
@geodro
geodro requested a review from a team as a code owner November 16, 2026 21:52
@geodro
geodro merged commit 982cefb into main Nov 16, 2026
1 check passed
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