Body: <p>I have just updated an environment running under IIS/Windows to CiviCRM 5.69.1. It's system status is Error with
  <a href="https://i.sstatic.net/13hbW.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/13hbW.png" alt="System status error message" /></a></p>
  <p>Running</p>
  <pre><code>composer civicrm:publish
  </code></pre>
  <p>gives</p>
  <p><a href="https://i.sstatic.net/IQECK.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/IQECK.png" alt="composer civicrm:publish result" /></a></p>
  <p>I have a similar problem on a development environment under 5.71.alpha1, where</p>
  <pre><code>composer civicrm:publish
  </code></pre>
  <p>does not error, but neither does it publish, so I still have the same error in the system status.</p>
  <p>Any suggestions?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T15:04:00.347Z
Comments.Text: It sounds like a really old version of civicrm-asset-plugin is there. When you upgraded did you just do civicrm-core? How are you upgrading?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T18:11:10.847Z
Comments.Text: I solved the problem on the 5.69.1 site by running:
  
  composer require civicrm/civicrm-asset-plugin
  
  This updated the plugin to 1.1.4.
  
  Running 
  
  composer civicrm:publish
  
  cured the issue, but I still have on my development site. This is why I haven't answered my query.
Comments.UserDisplayName: Stephen Palmstrom
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T18:30:58.733Z
Comments.Text: I 'solved' the problem in my development version by removing a newline from the end of  the version number string in:
  <drupal root>/web/libraries/civicrm/core\js/version.json.
  
  So it could be that composer civicrm:publish is working, but the verin number is being copied incorrectly.
Comments.UserDisplayName: Stephen Palmstrom
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-08T18:56:46.837Z
Comments.Text: The version.json was just fixed in master on the weekend, so depends how current your dev site core repo is.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-10T10:32:04.440Z
Comments.Text: Updating CiviCRM:
  composer require civicrm/civicrm-core:$VERSION civicrm/civicrm-drupal-8:$VERSION civicrm/civicrm-packages:$VERSION --update-with-all-dependencies --no-update
  followed by
  composer update
  This is because sometimes I am update Drupal as well, so combine the two into one composer update. 
  
  I suspect the civicrm:publish repo might have been out of date.
Comments.UserDisplayName: Stephen Palmstrom
Tags: <upgrade><composer>
Title: civicrm:publish
ThreadText: # civicrm:publish
  
  (Asked by: username_0 on 2024-01-08)
  
  I have just updated an environment running under IIS/Windows to CiviCRM 5.69.1. It's system status is Error with
  [![System status error message](https://i.sstatic.net/13hbW.png)](https://i.sstatic.net/13hbW.png)
  
  Running
  
  ```
  composer civicrm:publish
  
  ```
  
  gives
  
  [![composer civicrm:publish result](https://i.sstatic.net/IQECK.png)](https://i.sstatic.net/IQECK.png)
  
  I have a similar problem on a development environment under 5.71.alpha1, where
  
  ```
  composer civicrm:publish
  
  ```
  
  does not error, but neither does it publish, so I still have the same error in the system status.
  
  Any suggestions?
  
  **Tags:** upgrade, composer
  
  > **Comments:**
  > **username_1**: It sounds like a really old version of civicrm-asset-plugin is there. When you upgraded did you just do civicrm-core? How are you upgrading?  
  > **username_0**: I solved the problem on the 5.69.1 site by running:  composer require civicrm/civicrm-asset-plugin  This updated the plugin to 1.1.4.  Running   composer civicrm:publish  cured the issue, but I still have on my development site. This is why I haven't answered my query.  
  > **username_0**: I 'solved' the problem in my development version by removing a newline from the end of  the version number string in: <drupal root>/web/libraries/civicrm/core\js/version.json.  So it could be that composer civicrm:publish is working, but the verin number is being copied incorrectly.  
  > **username_1**: The version.json was just fixed in master on the weekend, so depends how current your dev site core repo is.  
  > **username_0**: Updating CiviCRM: composer require civicrm/civicrm-core:$VERSION civicrm/civicrm-drupal-8:$VERSION civicrm/civicrm-packages:$VERSION --update-with-all-dependencies --no-update followed by composer update This is because sometimes I am update Drupal as well, so combine the two into one composer update.   I suspect the civicrm:publish repo might have been out of date.  
  
  ---
  
  ## 0 answers
  
  