-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
ci: add check to ensure composer-bin is not accidentally committed #52080
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
Conversation
98cca28 to
b7422ba
Compare
| /** | ||
| * @var bool | ||
| */ | ||
| private static $installedIsLocalDir; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is coming in from the latest composer 2.8 update (composer/composer#12269). build/autoloaderchecker.sh only looks for changes to autoload_classmap and therefore our CI is not red since the latest composer bump.
b3d49f4 to
11764bd
Compare
11764bd to
dc53310
Compare
Signed-off-by: Daniel Kesselberg <[email protected]>
Signed-off-by: Daniel Kesselberg <[email protected]>
dc53310 to
3e9454a
Compare
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - name: Set up dependencies | ||
| run: composer i |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running composer install will install the dev dependencies again and therefore needs to go. I'm not so sure anymore, but still think that our state in github should not contain the composer-bin-plugin.
The drone workflow did not run composer install (see #43514 and https://github.com/nextcloud/server/blob/master/autotest-checkers.sh).
Requested @susnux as reviewer for a third look if that makes sense.
Summary
The composer-bin-plugin, as dev dependency, should not be committed.
TODO
Checklist