What happened?
Gemfury does not allow npm publish with custom visibility. It always publishes with the default visibility which is currently private.
Also, npm does not allow multiple publishes to the same version number. Currently, we remove the packages nightly and publish to npm with the same version, and as far as I understand, gemfury does not expose a way to programmatically update the visibility after the fact. This means each night the packages get set to private.
Stack Trace
No response
How can we reproduce the bug?
No response
Environment/Setup
No response
What happened?
Gemfury does not allow npm publish with custom visibility. It always publishes with the default visibility which is currently private.
Also, npm does not allow multiple publishes to the same version number. Currently, we remove the packages nightly and publish to npm with the same version, and as far as I understand, gemfury does not expose a way to programmatically update the visibility after the fact. This means each night the packages get set to private.
Stack Trace
No response
How can we reproduce the bug?
No response
Environment/Setup
No response