User tests: Successful: Unsuccessful:
Pull Request for Issue # .
npm ci
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Side effect the codemirror is updated because of the ranges in the package.json
Category | ⇒ | Administration com_media NPM Change Front End Plugins |
Status | New | ⇒ | Pending |
I assume the codemirror changes are not part of this pr?
Actually the lock already uses the 5.65.11
Lines 3152 to 3156 in 7f7e232
Hmm, the package lock shows also an update of skipto from 4.1.6 to 4.1.7. Ok for me, but not related to this PR and I'm not sure if ok regarding our rules for beta phase.
Hmm, the package lock shows also an update of the skipto plugin from 4.1.6 to 4.1.7
Richard, this is once again a problem deriving from the decision to use ranges in the versions when, for a project of this scale, the npm i
and npm ci
should return the SAME node_modules folder. FWIW the package.json has the correct version 4.1.7
https://github.com/joomla/joomla-cms/pull/39833/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R66 which for whatever reason was reflected wrongly in the lock file. The production team needs to set some rules on how and by whom the package-lock.json and the package.json could be modified. There are too many mistakes...
I have tested this item
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
Labels |
Added:
PR-4.3-dev
|
RTC
Labels |
Added:
?
NPM Resource Changed
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-02-13 04:56:26 |
Closed_By | ⇒ | obuisard |
Thank you Dimitris @dgrammatiko for the PR!
I assume the codemirror changes are not part of this pr?