You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Currently updating Evidence is a bit weird for me.
For example today I checked the version with npm view @evidence-dev/evidence version and the response was 39.1.13. Then I did a version upgrade in VSCode and I got a message back after a while that 2 packages were removed and 27 were modified. I then checked the version again and it was still 39.1.13 !!
IMO that should not be possible. If packages are removed, added of modified it is always connected to a release. Might be some dependencies but even then when you choose to upgrade dependencies in your project it should be a version bump. Having a few project with the same version can have different versions of packages I understand. That should not be possible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, Currently updating Evidence is a bit weird for me.
For example today I checked the version with
npm view @evidence-dev/evidence version
and the response was 39.1.13. Then I did a version upgrade in VSCode and I got a message back after a while that 2 packages were removed and 27 were modified. I then checked the version again and it was still 39.1.13 !!IMO that should not be possible. If packages are removed, added of modified it is always connected to a release. Might be some dependencies but even then when you choose to upgrade dependencies in your project it should be a version bump. Having a few project with the same version can have different versions of packages I understand. That should not be possible.
Beta Was this translation helpful? Give feedback.
All reactions