WebUi version number

[FallenRiteMonk]

On the WebUi the version of my private published package allways stays at the firt version i published. I published the versions 0.0.1 up to 0.0.4 of my package, but usig the WebUi it says v0.0.1 even though if i use npm view i get the correct 'dist-tags': { latest: '0.0.4' }

[dsuckau]

Yes, I have the same problem. I had package 0.1.1 and now published 0.2.0. The WebUI still shows 0.1.1 and even retrieves the README.md of 0.1.1, not the changed one of 0.2.0.

But when I npm install <mypackage>, I get 0.2.0.

[dsuckau]

Now after updating to sinopia 0.12.0 it tries to GET the README of my package 0.2.0, but it gets ERROR: No README data found! as response.

[rlidwka]

Now after updating to sinopia 0.12.0 it tries to GET the README of my package 0.2.0

Can you try to publish newer version of your package with the "latest" tag? That should work now (I mean, it now stores readme to a proper place).

[dsuckau]

Hm, now it's really weird. I tried it with a clean sinopia 0.12.0 without any packages.

I published a package 0.0.0 without a README. Everything okay, it displays the correct version string in Web UI and says, that there is no README.

After that I added a README to the package and published 0.0.1. The Web UI still shows version string 0.0.0 and the HTTP request to retrieve the README still points to 0.0.0 as well:

GET http://myhost/-/readme/mypackage/0.0.0

BUT it returns the README of 0.0.1 and displays it.

[dsuckau]

Now I did some changes to my existing README and published 0.0.2. Same behavior. Everything in the UI says 0.0.0, including the HTTP request. But the updated README is shown.

[rlidwka]

Hm, now it's really weird.

Now it stores just one readme per package, I believe this is how npm registry do it.

So version gets ignored. But version bug still exists, I'll have to look into it.

[vernak2539]

Happened to me also, but updated later (maybe a caching issue). Just some extra info if it helps.

1. on first package publish, version was correct (v0.0.1) on GUI index
2. on second package publish, version was not updated (v9.9.9) on GUI index
   • when i searched for the package in the UI it only returned the latest package (which is correct, yay!)
3. when different person published the same package with a different version (v0.0.55) the index page updated to that newly published package, but did not display v9.9.9 which is technically still the latest

Unpublishing yielded weird results as well, but that would probably be for a different issues. Basically unpublish didn't work initial via the GUI, but did on the command line. Then waiting a while the GUI updated accordingly.

[vernak2539]

This should be fixed by this pull #143

[rlidwka]

fixed in [email protected], thanks @vernak2539!