GitHub Community
Replies: 3 comments
-
|
Hello, I wanted to bring your attention to an issue I have been encountering with your library on GitHub. After investing considerable time in troubleshooting, I came across a relevant discussion on GitHub (https://github.com/orgs/community/discussions/54247) that seems to touch upon the same problem I am facing. It appears that there is a bug within the user interface (UI) of your library's repository, which is proving to be quite elusive to identify. This bug has led to confusion among users, including myself, regarding the behavior of the "latest" version. Although it returns the correct version "v6.0.0", in the UI it indicate that a different not relevant version will be returned "6.0.1-test.2". Also there is no visibility on other tags available to the user. I kindly request your attention to this matter and urge you to investigate the issue. Thank you for your attention. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
The "latest" channel is not only shown in the GitHub Packages interface. The package is actually published in the "latest" channel, even though it says:
This is completely incorrect behavior for the GitHub Packages registry! |
Beta Was this translation helpful? Give feedback.
-
|
+1, similar or same issue here as well https://github.com/orgs/community/discussions/54247 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Hello,
I'm trying to have distribution channels in Github Packages. I have a
latestversion as well asbeta,rc,next, and some custom ones. But no matter what I do, it always publish it aslatestFor exampe, I'm running
npm publish --tag nextand I do see in the console log the tag is set tonext.but it stills deploy the version as
latestchannel and doesn't create a pre-release namednext. it doesn't matter what the value I provide to tag flag, it always deploy withlatestPlease advice
Thanks
Eran
Beta Was this translation helpful? Give feedback.
All reactions