[#28160] - [4.0] Composer update joomla/database
- Fixed in Code Base
- 1 Mar 2020
- Medium
- Build: 4.0-dev
- # 28160
- Diff
- twister65:4.0-updb
- Pending Hound Hound is busy sniffing around... Details
User tests: Successful: Unsuccessful:
Summary of Changes
composer update joomla/database
This will update the joomla/database framework to the latest version.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Composer Change |
So FWIW on latest composer 1.9.3 and 1.9.0 - if I run composer update joomla/database then I don't get the metadata changes - but I also do not get a content-hash update :/
With version 1.9.3 of composer, if I run composer update --interactive and type joomla/database for the name of the package, I get this result. That's exactly what I did.
I just double checked, content-hash is a hash of composer.json. All this time I thought it had to do with the state of the lock file
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-01 21:03:16 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
?
|
||
Cool. Then we should be good here. Today I learnt too :)
How are you doing these updates? The lock file diff shows a bunch of other metadata updates and no hash update.
I don’t doubt you’re using
composer updateto do these things, but something hasn’t looked right in these PRs for some reason.