►
From YouTube: Introducing GitHub Package Registry
Description
Your code. Your packages. One login.
Watch the GitHub Package Registry’s surprise launch event with GitHub CEO Nat Friedman and lead developer, Phani Raj.
Sign up for the beta here: https://github.co/ytgpr
A
B
All
right,
how's
everyone
doing
on
a
Friday
awesome.
Thank
you
for
joining
us.
Welcome
to
github
we're
so
glad
that
you
could
commit
to
being
here
with
us
today.
I'm
matt
freedman
on
the
CEO
of
github,
we're
here
in
San
Francisco
at
github,
San
Francisco
headquarters,
but
github
is
actually
a
distributed.
Company
were
a
thousand
people
were
in
countries
around
the
world,
and
so
it's
appropriate
that
we're
also
streaming.
This
event
live
right
now
to
thousands
of
people
online.
B
So
wherever
you
are,
if
it's
Friday
night,
if
it's
Saturday
morning,
thank
you
for
joining
us,
we're
so
happy.
You
could
spend
part
of
your
day
with
us,
so
I
became
CEO
of
github
six
months
ago,
when
the
Microsoft
acquisition
completed
and
github
actually
operates
as
an
independent
company
and
we're
committed
to
serving
developers
and
giving
them
what
they
want,
and
so
some
of
you
may
have
noticed.
B
B
In
fact:
we've
shipped
over
the
last
six
months,
improvements
to
almost
every
part
of
github
from
draft
pull
requests
to
improvements
to
gist's
and
issues
and
notifications
to
new
mobile
views
like
the
one
we
shipped
yesterday
and
much
more
and
so
in
fact,
I'm
happy
to
report
that
at
the
six-month
mark
we've
shipped
over
a
hundred
updates
to
get
hub
in
just
the
last
six
months.
Something
we're
really
proud
of.
B
Everyone
at
github
has
worked
so
hard
to
do
all
this
for
you
and,
and
so
we're
really
proud
of
the
work
that
we've
done
and
we're
really
just
getting
started.
Now,
one
of
our
biggest
announcements
in
the
last
six
months
was
in
January
when
we
announced
that
we
would
make
unlimited
private
repos
free
for
all
a
github
users,
and
the
response
to
this
has
been
awesome.
We've
actually
seen
the
rate
of
private
repo
creation
on
github
triple
since
then,
and
with
no
slowdown.
B
In
fact,
an
acceleration
in
the
rate
of
public
repo
creation,
so
github
is
growing
kind
of
faster
than
ever
along
every
measurable
dimension.
As
an
example,
when
we
announced
that
Microsoft
was
buying
github,
we
had
28
million
registered
users,
and
today
we
have
36
million
registered
users
on
github.
We're
really
proud
of
that.
We
also
hit
thank
you.
B
We
hit
at
the
end
of
last
year,
a
big
milestone
with
a
hundred
million
total
repos
on
github.
Now
what's
interesting
about
this
is
to
look
at
the
rate
of
repo
creation,
so
it
took
six
years
for
github
to
get
to
its
first
three
million
repos.
Now,
today,
developers
create
more
than
3
million
repos
on
github
every
month,
so
github
is
really
growing
fast
and
it's
exciting
to
be
a
part
of
it
now.
I
know
you're
all
here
to
see
our
latest
work
right.
We
gave
a
little
teaser
Wednesday
morning.
B
We
announced
this
sort
of
mysterious
launch
event
and
we
invited
you
to
come
here
here
so
I
know
you're
curious
to
find
out
what
it
is
that
we're
shipping
now,
but
before
we
get
into
that,
a
lot
of
you
actually
made
some
pretty
great
guesses
as
to
what
the
announcement
would
be
today
and
so
I
thought
we
could
highlight
a
few
of
these
guesses.
So
here's
here's
three
Jaxon
Harper
suggested
that
we
ship
two
free
hours
of
dog
walking
for
all
github
pro
subscribers.
B
B
Now
Aaron
actually
works
again
up
and
we
are
very
proud
to
see
him
exemplifying
or
focus
on
performance
and
latency
with
this
idea:
Thank,
You
Aaron
and
finally,
many
of
you
made
the
same
suggestion
and
you
were
so
passionate
about
it
and
I
want
you
to
know.
We've
heard
you
you
want
Clippy,
you
really
want
clip.
You
can
get
hub,
but
I'm,
sorry
to
say
we're
not
shipping
Clippy,
yet,
okay,
so
to
understand
what
we
are
shipping
today.
B
I
want
to
just
take
a
step
back
and
explain
a
little
bit
about
how
we
see
the
world
and
software
development
a
github.
So
when
you
think
about
how
developers
write
software
today,
the
image
that
we
have
in
our
head
is
usually
the
image
of
the
loan
developer
right.
We
think
of
developers
as
loners
as
sort
of
introverts
who
work
by
themselves.
Maybe
in
a
darkroom,
you
know
with
the
door
closed,
just
them
and
their
computer
and,
like
you,
sort
of
slip
pizza
under
the
door,
and
you
know
you
get
code
out
the
other
side.
B
That's
the
archetype
right!
It's
this
archetype
of
Solitude,
but
in
reality
this
is
not
how
software
gets
created
right
and
in
reality,
software
development
is
deeply
collaborative
in
every
line
of
code
that
we
each
write,
builds
on
the
work
of
thousands
of
other
people,
we're
all
kind
of
all
a
part
of
this
interconnected
community,
where
each
person
who
writes
code
gets
to
leverage
and
build
on
the
work
of
others,
we're
standing
truly
on
the
shoulders
of
every
other
developer
who's
come
before
us,
and
so
that's
why?
For
us
it
get
up.
B
Our
mission
is
about
this.
Our
mission
is
to
build
the
global
platform
for
developer
cooperation.
It's
a
kind
of
a
magical
thing
we're
this
website
where
strangers
come
together
and
build
things
they
build.
The
future
together
and
like
in
2019
strangers
on
the
Internet
is
a
little
bit
of
a
scary
concept
right
and
so
the
fact
that
strangers
can
come
together
and
make
things
is
awesome.
B
B
B
B
B
Our
second
goal
was
to
help
teams
improve
their
velocity
and
be
more
efficient
and
productive,
adopt
best
practices
and
be
able
to
actually
automate
their
software
development
lifecycle
and
then
finally,
we're
really
focused
on
this
idea
of
security
and
Trust,
and
so
we
want
to
build
the
world's
most
secure
and
trusted
package
registry
that
can
link
your
code
to
your
commits
and
releases
all
the
way
through
to
your
packages.
So
you
have
that
full
traceability.
So
those
were
our
three
goals.
B
It
provides
both
public
and
private
registries
and
today
we're
shipping
out
of
the
box
with
support
for
five
registry
protocols,
NPM
rubygems,
nougat,
maven
and
docker
more
are
coming,
so
this
will
work
with
all
your
existing
packaging
tools
and
work
great
with
any
CI
system
that
you're
already
using
or
that
you
might
choose
to
use
in
the
future.
Okay,
the
best
way
to
understand
the
power
of
the
get
up
packaged
registry
is
to
see
it.
So
should
we
do
a
demo?
What
do
you
think.
C
Can
we
switch
the
screens,
please
hello,
everyone,
let's
slow,
wait
for
the
screen
to
turn
out
hey,
there's
my
dog.
Okay,
awesome
I
want
to
set
up
a
story
today
of
an
engineer,
who's
early
on
in
their
careers
and
they're,
trying
to
do
something
as
a
test
project
or
something
to
learn.
They've
just
learned
that
Khan
Academy
exists
and
it's
a
great
place
to
go
for,
go
for
them
to
learn
math,
science
and
other
stuff,
and
they
want
to
build
something
that
actually
works
with
Khan
Academy
and
they've
discovered
that
they
have
AP
ice.
C
C
Something's
interesting,
actually
just
turned
up
you've
seen
the
left-hand
side
under
issues.
You
have
a
new
result,
type
called
packages.
These
are
packages,
publish
to
get
ups
package
registry
across
all
of
Caleb
through
public
repositories
or
private
repositories
that
you
have
access
to.
So
this
gives
me
a
bunch
of
super
useful
information
such
as
what
is
the
package
type,
how
many
downloads
it
has
which
repository
it
comes
from
and
what
is
the
latest
version
and
when
it
was
last
updated?
If
there
were
multiple
results,
you
would
see
multiple
package
types
turn
up
here.
C
So
if
you're
looking
for
darker
packages,
you
can
click
on
the
darker
tab
down
there
and
you'll
see
only
darker
packages
going
forward.
So
let's
actually
follow
through
this.
So,
as
I
said,
I'm
a
developer
trying
to
build
something
that'll
work
with
the
Khan
Academy,
API
and
I,
see
that
there's
actually
a
whole
bunch
of
really
useful
information.
Here.
The
package
page
has
the
install
instructions
right
at
the
top
which
I
can
copy/paste,
but,
along
with
that,
I
also
have
download
counts.
C
All
of
the
versions
and
all
of
the
topics
that
the
Ridgid
repository
has
registered.
On
github.com
itself
now
I
know
who
published
this
so
I
can
just
look
at
this
directly
and
then
go
to
the
repos
code,
which
is
what
is
published
inside
the
package
and
see
who
wrote
it.
It's
just
one
contributor
it
mostly
meat.
So
there's
no
surprises
here.
C
It's
just
one
contributor
and
I
know
that
this
person
is
only
person,
who's
actually
contributed
code
and
I
can
look
at
what's
the
code
inside
this
so
now,
I
have
some
signal
of
trust
about
what
this
package
contains
and
who
wrote
it.
So
let
me
just
go
in
okay.
This
looks
great
so
now
I'm
certain
okay.
This
is
something
that
I
actually
want
to
import
into
my
application,
because
already
I
have
a
really
high
signal
of
trust
about.
C
C
I'm
gonna
create
an
empty
package
JSON
and
let's
run
our
npm
install.
Obviously
it
failed.
It
doesn't
know
what
suite
Haven
villages
or
anything
that
anything
there
is.
So
if
you
look
at
the
name,
sweet
Haven
village
is
the
name
of
the
organization
that
is
hosting
the
package
in
case
this
was
a
personal
account,
that'll
be
at
fanatic
as
your
username
or
at
your
company
name,
based
on
where
the
package
is
published.
C
So
I
need
to
log
in
to
log
in
I
need
to
do
something
that
people
are
pretty
used
to
doing
right
now,
creating
a
personal
access
token
on
github.com
itself
or
your
personal
account
as
part
of
package
registry.
We
introduced
two
new
scopes
which
are
pretty
low,
privileged
called
write
packages
and
read
packages
that
allows
you
to
only
work
with
packages
on
github
comms
repositories.
You
don't
need
to
give
this
thing
permissions
to
read
or
write
repository
sources.
C
C
We
want
publishing
packages
to
get
up
to
be
as
simple
as
changing
a
URL
and
then
you're
off
to
the
races
immediately
so
right
now
this
is
NPM
the
pkg
to
get
up
calm
as
I
show
you
more
demos
for
different
package
types,
it'll
be
darker
topic,
easy
calm,
NPM,
PKG,
calm
and
so
on
and
so
forth.
Where
every
one
of
the
types
we
support.
So
registry
is
npm
and
then
the
scope
is
the
organization
at
which
the
package
is
published.
That
was
that
and
then.
C
So
now
I'm
logged
in
this
is
a
stock
NPM.
Cli
I
didn't
have
to
write
anything,
it's
not
hacked.
If
you
want
later
come
more
and
I'll
show
you
the
hash
of
the
file,
and
you
can
compare
it
against
your
version,
so
I'm
gonna
now
run
and
Kim
install
now.
What
this
is
doing
is
it's
doing
a
couple
of
interesting
things.
C
It's
hitting
our
NPM
registering
API
it's
to
go
download
the
metadata
for
the
package
and
then
immediately
after
that
we
give
it
a
redirect
to
our
globally
available
CDN
so
that
your
package
download
is
fast.
No
matter
where
you
are
I
tried
this
from
my
home
in
Minneapolis
and
I,
found
out
that
the
CDN
is
actually
like
within
10
miles
of
my
house.
Hey
homegrown
packages
right
now,
I
go
back
to
the
package
and
then
it's
not
zero
downloads,
the
medication.
You
do
fresh
this
real
good,
hey
one
download,
perfect.
C
Thank
you.
What
you
see
up
there
is
the
download
activity
we
collect
and
roll
up
download
activity
by
the
hour
when
we
show
you
to
in
a
more
reasonable
format
of
the
year
so
far
the
month
so
far
week
so
far,
and
so
far
today
keep
an
eye
on
that,
because
there's
something
interesting
coming
up
there
pretty
soon.
So,
as
you
can
see
at
this
point,
let's
just
take
a
tiny
break.
C
What
you
looked
at
is
basically
me
being
able
to
search
for
a
package
using
your
existing
search
knowledge
in
the
same
search
box
as
you
always
search
for
code
on
get
up
comp
to
search
for
a
new
data
type
packages.
You've
been
able
to
use
your
existing
personal
access,
token
infrastructure
to
generate
a
token
that
will
help
you
install
packages
from
get
up
calm,
you
don't
need
to
learn
any
other
security
model
and
I
want
to
talk
a
little
bit
about
visibility.
C
This
repository
is
private.
The
only
reason
that
I'm
able
to
install
a
package
from
here
is
because
I
am
a
collaborator
on
that
repository
with
a
read-only
access.
So
even
though
I
generated
a
token
with
read/write
permissions,
if
I
do
not
have
right
access
to
the
repository
to
push
code,
I
cannot
publish
a
package
there.
Repository
permissions.
Are
your
registry
permissions?
C
If
you
can
push
code
to
the
repository,
you
can
push
a
package
if
you
can
read
code
from
a
repository,
you
can
download
stuff
from
our
positive
from
a
package
registry,
and
this
is
true
across
all
of
our
existing
package
types,
all
five
of
them.
So
if
you're
an
archive
in
who
manages
permissions
and
visibility
of
your
intellectual
property
through
repository
permissions
and
all
permissions,
you
can
continue
to
use
those
four
packages
starting
today,
ooh
right
all
right,
I
got
my
scriptures.
I
keep
going
right.
It's
hot
in
here!
C
Okay
packages
are
read
a
lot
more
than
encode
is
read
a
lot
more
than
it's
written
and
packages
are
downloaded
a
lot
more
than
than
they're
published.
The
statistics
I
have
is
like
96%
for
our
current
data,
96%
installs
and
4%
uploads.
So
let's
try
doing
that.
Let's
try,
uploading
the
package
so
to
do
that.
I
can't
use
this
login
anymore,
because
I
don't
have
permissions.
A
C
C
C
So
as
part
of
publishing,
what
it's
doing
is
it's
it's
calling
out
to
our
API
s
and
then
asking
for
an
upload
URL
for
it
to
send
all
of
the
content
up
and
pushing
the
file
up.
So
that
was
instant.
It
didn't
take
a
long
time
now.
If
I
go
into
my
packaged
page
here
and
refresh
this,
the
latest
tag
on
the
package
is
now
change
from
0
at
6.9
to
0.7,
dot,
zero
and
a
whole
bunch
of
stuff
was
automatically
generated
for
me
that
my
consumers
found
a
lot
of
value
in.
C
They
found
a
lot
of
value
and
automatically
generated,
install
instructions
and
again
automatically
generated
I.
Didn't
need
to
do
any
of
that
stuff
to
be
able
to
publish
a
package
onto
github,
Zen
p.m.
registry
and
there's
also
a
couple
of
stuff
in
here:
I
see
a
bunch
of
stuff
repeated
I'm,
a
neat
freak,
so
I
really
care
about
repeating
stuff
or
lower
again,
so
I
can
edit
the
description
of
a
package
via
marked
on
editing.
This
is
full
markdown,
editing
and
rendering
that
you
used
to
across
all
of
github
properties.
C
C
C
We
have
something
like
docker,
so
that
I
have
something
called
docker
kaa
like
kaa
light,
is
an
offline
version
of
Khan
Academy
that
you
can
run
in
your
CI
system
without
access
to
the
Internet,
so
that
you
can
run
your
test
against
it
at
this
point.
I
would
love
to
build
this
and
also
push
this
to
the
same
repository
that
hosts
the
application.
So
someone
downloading
the
library
can
also
use
the
docker
image
to
test
their
application
against
it.
So
to
do
this,
I
have
to
do
a
couple
of
things.
C
Are
you
usually
darker
build
an
in
darker
tag?
In
this
case,
I'm
gonna
skip
the
building
tag
part
and
do
the
both
at
the
same
time,
what
you
see
up
there
is
darker
dot,
PKG
github.com.
The
same
way:
you're
used
to
NPM
topic,
get
up
calm,
it's
darker.
Now
the
URL
is
pretty
much
the
same.
It's
sweet
heaven,
village,
Khan,
Academy
same
thing
that
you
did
back
for
the
NPM
package.
The
difference
is
now.
C
You
can
also
append
image
name
at
the
end,
along
with
an
image
tag
or
a
version,
if
you
call
it
that
so,
let's
call
this
one
dot
0.9,
because
I've
already
got
one.
That's
already,
there's
nothing
to
build
because
I've
already
built
it
a
couple
of
times
and
now
what
I'm
going
to
do
is
just
copy
this
and
before
I
push
I
have
to
login.
C
So
if
you
see
me
along
again,
that's
docker
is
a
domain
name,
but
the
token
is
pretty
much
the
same
as
the
token
that
I
used
for
accessing
packages
from
my
NPM
registry,
so
one
set
of
credentials,
gives
you
access
to
all
five
of
the
package
registry
types
for
every
github
repository.
Now,
that's
my
username
I'm
gonna
log
in
blah,
and
then
it's
push
again
native
tooling.
This
is
the
exact
same
darker
version.
That's
available
everywhere
asked
me
for
hashes
later
I'll
print
it
out.
C
It's
talking
about
layer
already
exists,
and
that's
because
of
the
way
that
the
doctor-client
works.
Every
image
is
split
up
into
multiple
layers
and
is
uniquely
identified
with
a
shot,
256
hash.
It
asks
our
server
hey.
Do
you
have
this
layer
already
and
then
we
say
yep.
It
is
so
if
you
have
a
repository
that
has,
that
is
a
monitoring.
What
is
producing
multiple
docker
images
and
they
all
share
the
base
image.
You
don't
need
to
upload
the
base
image
over
and
over
again.
C
You
do
it
once
and
every
other
docker
image
within
that
repository
will
have
access
to
it
immediately.
So,
let's
take
a
break
here
and
then
talk
about
what
we
just
saw.
We
saw
the
ability
for
you
to
generate
a
token
that
not
only
gives
you
read
access
but
also
write
access
to
all
packages
on
github
comms
package
registry.
C
You
saw
that
the
URLs
domain
name
is
pretty
specific
and
pretty
uniform
across
all
of
the
package
registry
types,
how
the
urls
are
formed
and
also
what
you
need
to
do
to
be
able
to
publish
a
package
to
github
package
registry.
Now
you
might
be
saying
okay.
This
is
all
great,
but
no
one
on
my
team
does
this
like
no
one
on
my
team
actually
directly
pushes,
via
the
npm
CLI
of
the
docker
CLI
via
automation,
in
place
for
that
stuff,
yeah
robots
doing
our
work
for
us.
C
So
let's
get
a
robot
to
do
something
for
us
to
do
that.
I
have
a
separate
application
here
called
package
cloud.
It's
a
it
has
nothing
to
do
with
package
registry
unfortunate
naming.
It
basically
allows
you
to
work
with
different
cloud
providers
such
as
AWS,
ECR
and
Amazon,
and
it
helps
you
create
virtual
machines
and
stuff.
So
this
team
is
pretty
specific
about
the
kind
of
product
that
they
want
to
build.
They
want
everything
to
have
a
URL,
so
what
they
do
is
for
every
cool
request
that
is
merged
to
master.
C
They
want
to
have
the
ability
to
point
it
back
to
a
package
that
was
produced
out
of
that
hash.
So
what
that
means
is
master
is
always
deployable.
Is
the
philosophy
that
we
follow
here
it
get
up.
So
for
a
bunch
of
you
were
curious
about
setting
up
a
workflow
that
says,
master
is
always
available
as
a
redistributable
package.
This
is
something
that
might
be
useful.
This
will
replace
pretty
simple.
It
says
when
a
PR
is
merged,
published
to
pull
github
package
registry
and
then
comment
on
the
PR.
C
Now,
let's
make
a
really
contrived
example
here
and
then
I'm
going
to
change
this
and
to
do
that.
I'm
gonna
do
this
and
then
I'm
gonna
call
wonder
they
know.
Let's
go
back
and
I'm
gonna
get
out
of
full
screen,
so
I
can
actually
see
this
so
1.5
and
then
I'm,
saying
I'm,
gonna
say
it's
not
amazing.
It's
incredible
preview.
C
So
let's
have
this
side-by-side.
So
at
this
point
a
bunch
of
the
collaborators
from
the
repository
have
come
in.
They
have
looked
at
this
and
they're
like
this
makes
a
lot
of
sense.
Thank
you
for
doing
this.
For
us
this
is.
This
is
useful
and
I'm
like
you
know.
What
thank
you
so
much
I
look
to
serve
and
we
merge
this
to
master
at
this
point.
C
I
want
a
bunch
of
robots
to
kick
off
for
me
and
let's
make
sure
that
our
robots
are
doing
something
and
to
ensure
that
there's
no
trickery
here,
I'm
just
going
to
slowly
back
away,
let's
refresh
this
okay
great,
so
it's
doing
something
I'm,
just
gonna
walk
away
to
make
sure
it's
nothing.
So
my
prediction
is
that
I
believe
in
calling
your
shots.
My
prediction
is
that
at
a
certain
point
a
package
will
get
pushed
somewhere
and
someone
will
comment
on
something
all
right.
Let's
wait!
Oh
the
GPR
action.
C
C
C
Thank
you.
You
guys
can
sense
what
I'm
thinking
I
don't
know
how
so
that's
the
package
is
published.
Now
it's
also
available,
so
you
can
also
will
this
just
switch
to
little
Dew
and
everything
that
you
just
saw
is
also
true
just
because
it's
automation
doesn't
mean
that
you
have
to
learn
a
new
set
of
tools.
It's
the
same
access
token
that
you
created
to
be
able
to
work
from
your
local
machine,
that's
also
working
from
within
your
automation
system
and
also,
if
you're,
the
kind
of
person
who
leaves
your
keys
hanging
about.
C
I
think
this
is
extremely
powerful
today,
if
you
have
to,
if
you
have
a
repository
that
publishes
the
docker
image
and
also
an
NPM
package,
you
need
to
maintain
two
sets
of
accounts
and
two
sets
of
credentials
and
two
sets
of
role
mappings
and
everything
just
so
that
you
can
manage
relationships
and
packages
across
multiple
vendors.
Again,
a
package
registry
allows
you
to
use
your
existing
tooling
and
existing
knowledge
to
work
across
all
five
of
the
package
registry
types
we
support
not
just
mentioned.
C
C
So
if
you're
an
our
guide
man
or
someone
who's
looking
out,
so
if
you're
part
of
an
organization
you
saw
my
dog
go
look
for
packages
on
github.com.
So
if
you're
an
engineer
and
you're
thinking,
what
does
my
organization
do
for
XYZ?
Who
do
I?
Ask
for
organizational
knowledge
about
I
want
to
work
with
elasticsearch
or
I
want
to
work
with
docker
I
want
to
work
with
octo
kit
or
get
up
api's
I
want
to
see
what
is
my
organization
using
for
packages
in
terms
of
consumption
and
also
production.
C
C
This
also
supports
search,
see
like
again
search
everywhere,
so
I
think
that's
like
pretty
much
all
of
the
stuff
that
I
wanted
to
cover
at
this
point
like
and
that's
gonna
mention
a
couple
of
other
things
in
closing.
I
want
to
say
a
couple
of
a
couple
of
things.
It's
been
a
pleasure
to
build
as
a
github
and
I
think
in
terms
of
support.
A
planet-scale
application
requires
planet-scale
support.
I.
C
Think
github.com
is
a
planet-scale
application
and
get
a
package
registries
of
planet-scale
service
that
is
built
to
support
its
needs,
and
nowhere
is
it
more
relevant
than
something
that
is
already
happening
today.
For
us,
elasticsearch
is
an
image
that
is
used
inside
our
CI
systems
every
hour.
This
image
is
downloaded
at
least
10
times
and
get
up
deploys
to
get
deploys
the
entire
website
about
at
least
five
times
of
five
times
a
day,
depending
on
the
queue
length.
C
Some
people
might
disagree,
but
when
640
engineers,
that's
our
engineering,
org
know
where
you
live
and
also
having
a
phone
number.
They
will
call
you
if
what
you
will
fails
them
when
they're
trying
to
deploy
to
github.com
or
the
past
six
months.
I've
got
not
gotten
a
single
call,
so
that's
pretty
great.
We've
powered
just
this
year
about
half
a
million
downloads
of
our
darker
image.
And
if
you
look
at
this
image,
it
is
not
small.
C
What
you
look
at
here
is
basically
the
manifest
information,
but
that
image
is
about
1.5,
GI
excellence,
half
a
million
times
1.5
gigs
now
I'm,
not
a
math
specialist,
but
that's
a
lot
isn't
so
good.
Github
and
I'm
really
proud
to
be
part
of
this,
because
I
believe
that
get
up
relies
on
this
and
I
think
because
we
rely
on
it.
We
can
promise
that
you
can
too,
with
that.
Thank
you.
B
Thank
You,
potty
I
hope
you
liked
what
you
saw.
To
recap.
A
few
of
the
kind
of
key
highlights:
whoopsie
Oh,
public
and
private
registries
are
supported
on
github
package
registry
number,
one
two.
We
have
a
single
ball
again,
a
single
account
that
gives
you
access
to
all
of
your
registries
and
your
code.
So
you
can
control
access
to
your
code
and
packages
from
a
single
set
of
permissions.
It's
really
powerful
support
for
the
five
major
registries
mentioned
here
and
more
coming
soon.
B
We
have
a
great
extension
framework
for
adding
support
for
new
registries,
which
will
be
opening
up
in
the
future.
This
works
with
any
CI
and
as
paani
demonstrated
for
you,
it
also
works
with
get
up
actions
which
is
really
exciting.
We
have
full
graph
QL,
API
and
webhook
support.
So
if
you
want
webhooks
based
on
papac
package,
just
getting
published
that
sort
of
thing
you
can
get
them,
we
provide
insights,
download,
stats
and
analytics
for
maintainer
x',
and
it's
really
fast.
We
use
a
global
CDN
to
distribute
the
packages
everywhere.
B
So,
wherever
you
are
in
the
world,
a
copy
of
the
package,
you're
looking
for,
is
probably
cashed
in
near
you,
so
we're
launching
in
beta
today
and
if
you
want
to
get
access
to
the
beta
you'll
be
able
to
sign
up
during
the
beta
github
package
registry
is
completely
free.
We're
also
committed
free,
beta,
yeah
glad
you,
like
I,
don't
know
who
charges
for
their
betas
but
but
we're
also
committing
today
that
get
a
package
registry
will
be
free
for
public
repositories
forever.
B
So
across
all
registry
protocols
across
all
types
and
after
it's
generally
available
after
the
betta
goetta
Package
registry
will
be
included
in
all
of
our
paid
plans.
So
we'll
have
more
details
on
that
after
the
beta
and
when
we
get
the
GA,
but
we're
committed
to
including
the
capabilities
and
all
of
our
paid
plans.
Now
we're
also
really
excited
to
be
working
with
the
open
source
community
on
this
right
I
mean
get
her
packaged
registry,
our
entire
model
of
how
developers
work
depends
on
their
being
a
healthy
and
thriving
open
source
community.
B
So
we're
excited
to
already
be
cooperating
with
our
friends
at
NPM
and
yarn
and
we're
looking
forward
to
working
more
with
them
in
the
future,
so
stay
tuned
for
more
to
come.
Okay,
if
you're
interested
in
you
want
to
know
how
to
get
started,
you
can
sign
up
for
the
beta
now
at
this
URL
github.com
/features
/font.
B
Cisco,
we've
already
turned
this
on
in
your
accounts.
It
should
show
up
in
the
next
couple
of
hours
we
used
the
email
address
that
you
gave
us.
So
if
you
gave
us
a
fake
email
address,
it
probably
won't
work,
but
you
should
have
access
soon,
also
Pawnee
and
some
of
the
other
folks
who've
been
involved
in
building
the
get
a
package
registry
are
going
to
be
here
in
the
back
of
the
room.
B
Buy
those
expensive
leather
benches
back
there,
and
so,
if
you
want
to
ask
them
questions,
you
can
go
talk
to
them
for
everyone
everywhere.
We'd
really
love
to
hear
your
thoughts,
your
requests,
your
feedback,
what
you
like,
what
you
don't
like
we're
in
this
for
the
long
term,
we're
totally
committed
to
offering
the
service
and
being
the
best
in
the
world,
and
so
we'd
love
to
hear
what
you
think
we're
listening
now.
This
is
kind
of
the
beginning
of
a
very
busy
time
at
github
or
we're
kind
of
entering
this
really
exciting
season.
B
And
so,
in
fact,
in
less
than
two
weeks
we
have
one
of
our
major
conferences,
which
is
called
github
satellite.
It's
on
May
23rd
and
it's
in
Berlin,
and
so,
if
you're
in
Berlin
or
nearby
we'd
love
to
see
you
in
person,
you
should
please
come
visit.
If
not,
you
know
watch
for
the
announcements
that
we're
going
to
be
making
there.
Some
of
them
are
incredibly
exciting
and
we
can't
wait
to
share
them
with
you
later
in
the
summer.