►
Description
I setup a quick pipeline that publishes and npm package and demonstrate the data showing up in the package details page
A
Hello,
I'm
Tim,
the
product
manager
for
the
packaged,
a
jacket
lab
and
today,
I
want
to
do
another
speedrun
this
time
talking
about
a
feature
that
is
a
currently
available
on
get
babcom
and
will
be
released
in
the
upcoming
milestone,
12.8,
and
so
this
feature
is
adding
gitlab
metadata
to
package
information.
So
if
you
built
a
package,
whether
that's
with
NPM
or
maven,
or
Conan
I'm
using
git
lab
CI,
we
will
now
begin
to
add
the
pipeline.
Id
branch
commit
and
commit
to
the
meta
death
to
the
package.
Details
page.
A
This
came
out
of
some
user
research
that
we
did
that
people
were
saying
that
they
navigate
to
the
package
registry
to
be
able
to
verify
that
a
package
was
built
correctly
or
to
troubleshoot
when
something
has
gone
wrong
and
since
the
majority
of
packages
are
built
using
CI,
we
wanted
to
make
sure
that
we
added
this
additional
build
information
in
there.
Okay,
so
I
have
a
project
here,
I
just
that
will
build
a
basic,
build
and
publish
a
basic
NPM
package,
I'm
doing
it
via
CI
I,
actually
copied
this
information
from
our
documentation
called.
A
We
have
a
section
for
publishing
a
package
with
CI
CV,
and
this
has
just
some
basic
goal:
some
basic
information
that
had
to
publish
using
the
CI
job
token
a
couple
of
changes
I
made
here
so
I
had
to
fill
in
my
project
ID.
You
could
find
this
and
if
you
click
on
your
project,
let's
see
it's
just
here
as
part
of
right
underneath
the
project
name
so
I
included
that
and
then
I
also
am
going
to
tag
the
the
package
when
I
publish
it
with
the
tag
speedrun
just
to
show
off
the
tags
feature.
A
A
Let's
see
okay,
so
when
you
publish,
if
you
attempt
to
publish
a
package
of
the
name
that
already
exists,
you
will
receive
a
403
forbidden
error.
I,
don't
love
that
error,
but
I
think
what
I
need
to
do
is
just
go
to
my
repository
and
find
my
package
JSON
file
and
I'm
just
gonna
bump
up
the
version.
One
minor
version
here:
I'll
change
it
to
version
2.0
point
three
and
I'll
just
make
my
commit
message:
okay,.
A
I
ran
this
on
master
as
well
as
the
command
and
if
I
wanted
to
I
can
copy
the
comitia
as
well.
So
that
is
the
the
first
piece
of
us.
Adding
this
additional
get
lab
metadata.
I
also
wanted
to
just
briefly
bring
up
this
epic
that
we
have
that
details.
Some
of
the
additional
user
interfaces
changes
that
we're
going
to
make
for
the
packaged
registry.
So
these
are,
you
could
click
on
all
of
these
issues
and
you
could
navigate
and
see
some
of
the
designs
and
join
the
conversation,
but
at
a
high
level.
What
we're?
A
What
we
would
like
to
do
is
introduce
a
versions
tab
to
the
package.
Details
UI,
so
you'll
be
able
to
see
different
versions.
We'd
like
to
display
more
robust
historical
data
about
the
package
include
more
information
in
the
title
section,
and,
and
just
generally
we
want
to
add
more
metadata.
We
want
to
make
it
easier
to
verify
that
the
package
is
being
built
correctly
and
to
troubleshoot
when
something
has
gone
wrong,
because
that
that
is
the
primary
reason
that
people
navigate
to
this
section
of
the
user
interface.