Hacker News new | ask | show | jobs
by sytse 2603 days ago
GitLab released integrated packaging back in 2016 - starting with a Docker registry - and adding Maven and NPM in 2018. You can find our plans for adding further packaging capabilities on our public packaging roadmap https://about.gitlab.com/direction/package/

We are also embarking on making package management more secure and auditable for the users of packages with a Dependency Proxy https://about.gitlab.com/direction/package/dependency_proxy/ GitLab users will be able to block and delay packages that are suspect and trace where vulnerable packages were used. This will increase performance, cost efficiency, and the stability of your tests and deployments.
1 comments
jbergstroem 2603 days ago
> GitLab released integrated packaging back in 2016 - starting with a Docker registry - and adding Maven and NPM in 2018.

No, first version with "NPM support" (see my other comment as why I don't consider it being "supported") was gitlab 11.7, end of january 2019. I was really looking forward to this and were following your verdaccio (an open source npm registry) thread closely. Development then made a 180 and chose to re-implement rudimentary support for npm on top of your current package abstraction instead.

link
sytse 2603 days ago
Oops, you're correct that 11.7 was the first release, sorry for messing up the timeline.
link