►
From YouTube: GitLab 13.10 Kickoff - Package:Package
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
I'm
tim,
I'm
the
pm
for
the
package
stage
at
gitlab,
and
today
I
was
going
to
do
a
quick
review
of
some
of
the
issues
we
have
planned
for
milestone.
1310,
I'm
just
going
to
highlight
four
issues
today:
two
that
are
some
nice
usability
improvements
to
the
package
registry
user
interface.
A
The
first
is
adding
the
gradle
setup
and
install
commands
to
the
package
detail
page
if
you've
seen
this
before,
you
may
have
seen.
We've
had
these
install
and
setup
commands
for
maven
and
we've
kind
of
and
we've
not
included
them
for
gradle
in
the
past,
and
we
and
we
see
a
pretty
equal
distribution
between
maven
and
gradle.
So
this
issue
will
support
these
commands
and
you
can
toggle
between
showing
gradle
and
showing
maven
commands,
whichever
one
you
prefer.
A
So
what
we're
talking
about
here
is
that,
basically,
if
you
have
published
many
versions
of
a
of
a
given
package,
this
history
could
be
very
long,
and
so
what
we've
done
is
we've
prioritized
showing
the
most
recent
five.
The
earliest
five,
and
then
you
can
kind
of
see
that
we
show
we
hide
the
history
in
between.
So
you
can
see
for
this
particular
package.
There
was
284
hidden
updates.
So
if
I
click
this
button
to
show
full
history,
you'll
be
able
to
expand
and
see.
A
All
of
the
updates
that
have
happened
for
this
particular
package,
so
really
excited
about
those
usability
improvements.
The
other
two
issues
I'll
just
highlight
these
are
ones
that
carried
over
from
13.9
that
we'll
be
working
on
in
1310,
so
they,
but
they
should
be
available
on
gitlab.com
within
a
week
or
two.
The
first
issue
just
to
touch
on
quickly,
is
removing
or
is
lifting
the
naming
convention
requirement
for
the
project
level
api
for
publishing
npm
packages.
A
So
previously
you
had
to
match
the
scope
name
to
your
gitlab
path,
which
was
really
frustrating,
because
if
you
had
your
company
name
started
with
a
capital
letter,
then
basically
you
weren't
able
to
use
the
npm
public
registry
because
they
do
not
allow
capital
letters.
So
this
might.
This
change
will
hopefully
make
this
registry
a
lot
more
easier
to
use,
especially
in
conjunction
with
the
npm
public
registry
and
then
another
change
that
we're
working
on
is
supporting
pulled
by
digest
in
the
dependency
proxy.
A
So
one
thing
that
we've
seen
is
people
that
are
using
this
feature
are
running
into
errors
when
using
docker
20
x.
So
this
change
will
fix
that
issue
and
which
should
be
available
on
gitlab.com
in
the
coming
weeks
and
it
will
be
included
in
the
1310
release.