►
From YouTube: GitLab 14.2 Kickoff - Package:Package
A
A
The
first
one
is
an
improvement
to
our
pi
pi
rep
repository.
So
right
now
you
can
use
your
git
lab
project
to
publish
any
type
of
python
packages.
You
can
install
them
using
a
group
endpoint
as
well,
but
all
these
packages
have
to
be
hosted
on
gitlab.
What
we
would
really
like
to
do
is
offer
you
the
ability
to
say
if
you
try
to
install
a
package
from
your
gitlab
project
or
group,
and
it's
not
found
look
for
it
in
the
public
pipi
repository.
A
This
is
a
step
forward
in
our
direction
towards
proxying
and
caching
packages
from
external
remotes,
but
hopefully
this
makes
your
life
a
little
bit
easier.
The
next
issue
that
I
wanted
to
mention
is
adding
deploy
token
support
for
the
dependency
proxy.
So
right
now
you
can
use
the
dependency
proxy
to
proxy
and
cache
images
from
docker
hub,
but,
and
you
can
authenticate
using
your
job
token,
and
then
we
also
have
some
predefined
environment
variables
that
you
can
use.
But
a
lot
of
customers
rely
on
deploy
tokens
for
authentication.
A
A
And
finally,
the
last
issue
is
an
improvement
to
our
npm
feature
for
the
package
registry.
So
right
now
you
can
use
the
package
registry
to
publish
and
install
all
of
your
node
packages
and
you
could
use
npm
or
yarn.
One
of
the
problems
is,
though,
that
not
all
of
the
metadata
from
the
package.json
file
is
extracted
and
presented
in
the
user
interface,
so
this
makes
it
hard
to
validate
that
you're
using
the
correct
package.
A
It
also
means
that
gitlab
isn't
the
single
source
of
truth
for
all
of
your
package
metadata.
So
we'd
like
to
improve
that
by
ensuring
that
when
a
package
is
uploaded
to
the
registry,
we
extract
all
of
the
relevant
metadata
from
the
package.json
field
file
and
then
present
it
in
the
user
interface
and
return
it
in
the
api.