Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Invalid manifest file error for all packages in universal feed



  • Hi,

    I'm seeing "Invalid Manifest File" errors all over our universal feed.

    ca90fb33-6c0a-44ee-a60c-c1cf88867e3a-grafik.png

    3cd2fdd9-0d1e-4830-a6e8-82f9168d07d0-grafik.png

    My packaging/uploading CI jobs using the upack utility stopped working with a similar error.

    65927b5b-9f08-4422-87b0-150115a0a7c2-grafik.png

    According to the manifest spec the createdDate timestamp has the wrong format, which now leads to this error.

    From the point of time since the packaging errors started happening I conclude this must have been introduced by ProGet release 24.0.23.

    Now two questions:

    1. Is there anything I can do about the malformed manifests already uploaded to ProGet?
    2. Will there be a CLI tool for creating Universal Packages which correctly formats the timestamp for the manifest file? Current State seems to be
      • Upack still formats the timestamps in the wrong way and seems to be discontinued.
      • PgUtil does not include the functionality of the upack tool (yet?) despite someone sayin so in this issue
        0af721bd-9880-41a5-a688-fb05c4ef0c04-grafik.png

  • inedo-engineer

    Hi @arose_5538 ,

    Looks like this was indeed a regression in 2024.23 as a result of upgrading the JSON library we were using... I guess it's a lot more strict.

    Of course, upack is also wrong, but for whatever reason it worked before. anyway it's an easy fix, and will be fixed in the next maintenance release (scheduled Feb 7) of ProGet via PG-2884.

    In the meantime, you can just downgrade to 2024.22.

    And I checked pgutil 2.1.0 will be released soon :)

    Cheers,
    Alana


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation