[#35084] - [4.0] composer update
- Fixed in Code Base
- 10 Aug 2021
- Medium
- Build: 4.0-dev
- # 35084
- Diff
- brianteeman:composer4check
User tests: Successful: Unsuccessful:
Dont really understand why but when I run composer update (after the latest commits by @wilsonge) i get a new and different composer.lock file
From what I can see the difference is that my version includes more funding and support links
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Composer Change |
But I can confirm I get the same changes as made by this PR here when running "composer update" on a clean, current 4.0-dev branch as of now. Am working on Linux.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35084.
I am using the very latest release
Composer - Dependency Manager for PHP - version 2.1.5
2.1.3 here.
I'm on 2.1.3 too. So I dunno especially if @richard67 is on the same version of me but gets the same as you brian...
Either way looks fine, merging
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-08-10 20:34:17 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
Composer Dependency Changed
?
|
||
cool
I can see only differences in support and funding except of one URL change from
"url": "https://github.com/joomla-framework/mediawiki-api.git"to"url": "git@github.com:joomla-framework/mediawiki-api.git",which also has a related change a few lines below ("default-branch": true,added), and for one other package the "abandoned" property has been removed. But there is not really an update between current 4.0-dev and this PR here. So I think it doesn't really make a difference.