►
From YouTube: Pajamas UI Kit 16.1 release notes
Description
Foundations product designers, Dan Mizzi-Harris and Jeremy Elder, walk through the latest release notes to highlight and explain the latest updates.
A
So
all
right,
16.1
UI
kit,
pajamas
UI
kit,
release
notes.
Fortunately,
this
time
Dan
is
able
to
join
me
so
that
it's
not
just
me
narrating,
and
so
we
could
have
a
little
more
conversation.
I
will
start
by
saying
Dan.
Thank
you
for
all
of
your
massive
effort
in
not
only
this
release
with
UI
kit,
but
but
just
what
you
bring
to
the
team
super
helpful
and
I
hope.
Others
also
sense
the
same
and
benefit
from
that
like
I
have
so
all
right.
A
Welcome
to
the
16.1
release,
notes,
the
release
notes
are
I
will
go
ahead
and
share
so
that
you
have
some
context
here.
Release
notes
are
what
we're
publishing
on
the
pajamas
website
under
get
started.
Pajamas
UI
kit
release
notes,
and
it
is
for
the
pajamas
UI
kit,
which
is
all
of
our
figma
assets,
that
we
distribute
that
have
libraries
the
designers
can
use
to
design
for
gitlab
and
the
release
notes
we're
capturing
once
per
milestone.
A
All
of
the
additions
enhancement,
changes,
fixes
removals
notes,
Etc
that
relate
to
those
files
I'm.
We
don't
do
any
other
versioning
of
the
file
other
than
this,
and
so
by
releasing
once
a
milestone,
it
provides
a
predictable
opportunity.
So
that's
where
you
what
they
are
where
to
find
them.
You
can
view
the
history.
We
started
this
on
1511
and
we
will
continue
onward
as
long
as
it's
helpful.
So
on
that
note,
please
let
us
know
if
this
is
helpful.
B
So
we'll
see
how
the
release
note
starts
a
little
bit
differently
in
that
it
talks
about
next
release,
rather
than
the
release.
That's
just
happened,
but
we
wanted
to
give
everyone
a
little
bit
of
a
a
heads
up,
because
we
think
it's
going
to
be
a
little
bit
disruptive
and
we're
not
able
to
prevent
it
completely.
B
Some
of
the
latest
fixes
and
optimizations
from
inter
some
of
the
really
good
stuff
is
some
clearer
render
rendering
of
certain
characters,
especially
at
some
of
the
higher
weights
and
at
smaller
sizes
as
well.
What
happens,
though,
is
some
line.
Lengths
increase
and
decrease.
It
decrease
for
the
larger
sizes
increase
for
the
smaller
sizes.
This
is
expected,
but
we're
not
able
to
update
the
fonts
for
everyone
in
an
opt-in
way.
B
The
fonts
are
set
at
the
org
level
in
figma
and
they're
just
aren't
or
off
it's
a
little
example
of
this
I've
pulled
in
a
beta
version
that
we've
been
doing
some
testing
with
here's
how
it
rendered
before
when
it
was
quite
large.
This
is
96,
but
the
new
render
you
can
see
the
old
one
in
the
red
and
the
new
one's
a
lot
more
compact
looks
better,
but
the
this
shifting
of
sizes
might
cause
some
layout
changes
in
your
files.
B
If
you've
got
any
concerns
about
this,
for
example,
you're
running
some
user
Testaments
and
prototypes
at
a
certain
time
during
the
last
week
or
so
of
the
Milestone
do
reach
out
to
us,
and
we
can
see,
see
how
we
can
help
work
around
that
and
any
suggestions
we
might
have
when
the
fonts
get
updated
at
the
old
level.
It'll
affect
all
of
the
files
immediately
as
a
positive
in
this
Milestone
we'll
be
updating
the
type
scales
for
some
of
the
headings
and
getting
them
implemented
in
gitlab.
B
Ui
they've
been
out
of
sync
for
a
while
now
so,
hopefully,
by
the
end
of
this
Milestone
start
to
the
next
one
and
we'll
be
well
on
our
way
to
having
the
typography
and
figma
match
the
typography
in
a
design
system
and
gitlab
UI
a
match
of
typography
in
the
product
which
will
hopefully
make
collaboration
handovers
and
my
reviews
all
of
that
sort
of
stuff.
A
lot
easier,
so
yeah
any
concerns
do
do
reach
out,
but
there's
no
way
to
opt
in
to
this
to
this
one,
it's
going
to
affect
everyone
all
at
once,.
A
Awesome
and
up
next
is
some
changes
to
icons.
So
there's
a
few
added
I
won't
list
everything
here,
but
take
a
look
at
that.
A
few
additions
and
a
few
enhancements
Julia's
been
amazing
at
contributing
to
iconography
and
illustration,
and
so
there's
some
really
good
enhancements
to
Optical
sizing
for
some
of
the
editor
icons.
A
B
B
Guess
it's
similar
to
how
we
display
them
on
comments
and
notes
and
activity
anyway,
that
this
adds
it
to
gitlab
UI
in
this
format,
so
it
the
Styles,
will
be
consistent
across
to
support
that
we've
added
it
to
the
UI
kit
instances
as
well.
You
can't
pull
us
through
as
a
component,
but
if
you
want
to
copy
and
paste
it
out
to
know
that
you're
using
styles
that
match
you
can
do
that.
B
Also,
while
we're
here,
there
are
some
fixes
later
on,
we'll
talk
about
some
of
the
things
we've
removed,
one
of
them
being
the
badges,
and
there
were
some
instances
and
components
that
were
hanging
on
and
still
using,
the
old
version
of
the
badge.
These
Stacks
instances
were
one
so
they've
been
updated
to
use
the
most
up-to-date
badge
components
and
there
are
some
hidden
ones
in
these
menu
items.
B
B
Don't
worry
about
the
strange
shapes
and
positions
when
they're
visible
they
display
as
they
should,
and
we
also
updated
the
color
swatch
to
use
a
check
box
that
is
from
the
design
system,
rather
than
over
time.
It
become
disassociated
from
anything.
So
that's
updated,
so
you
might
see
an
update
here
or,
if
you're
pulling
through
this
Color
Picker,
you
might
see
some
updates
there.
A
Go
to
the
last
item
here
is
something
it's
it's
rather
large
in
the
sense
of
I
guess
the
impact
to
the
file
itself,
maybe
not
your
use
case
if
you've
already
migrated,
but
we
have
several
items
that
have
been
in
deprecated
status
for
for
some
time
now
at
least
a
milestone
minimum
for
our
our
guidelines,
but
most
of
these
getting
closer
to
a
year
potentially.
So,
if
you
haven't
migrated
any
of
these,
there
are
links
where
you
can
find
the
new
ones.
A
If
you
need
any
help
with
that,
please
let
us
know
you
can
always
refer
to
the
file
history.
If
you
need
to
retrieve
an
old
design
artifact
any
of
your
files
that
use
this
will
will
continue
to
use
it.
It
just
won't,
be
updated,
it'll
be
more
like
a
detached
state,
so
these
were
removed,
jump
over
into
figma
actually
before
I.
A
Do
that,
if
you're
curious
about
our
deprecation
process,
you
can
you
can
look
at
that
under
the
figma
guides,
breaking
changes,
we
we
have
a
section
on
deprecation
and
then
what
that
means
and
and
how
we
think
about
it.
So
I
would
encourage
you
to
to
become
familiar
with
that,
if,
if
you
would
like
and
then
in
figma
once
again
viewing
the
history
of
the
UI
kit,
in
this
case,
the
component
Library
specifically
just
jump
back
several
versions
before
the
deprecations
happened,
to
show
you
the
before.
So
we
have
a
deprecated
section.
A
All
the
items
are
under
the
deprecated
section.
All
of
these
have
been
removed
in
this
latest
release
this.
This
should
do
a
few
things.
One
is
it's
going
to
enable
your
file
to
be
more
performant,
but
also
as
we
do
future
changes.
These
are
lingering
things
that
since
they're
in
the
file
and
use
styles
of
the
same
name,
they
also
get
updated.
So
even
though
they
were
deprecated
at
a
certain
State,
they
might
still
inherit
new
changes,
which
we
really
want
to
avoid
if
possible.
A
Because
then
you
won't
have
an
accurate
picture
of
the
the
artifact
at
the
time
of
deprecation
unless
everything's
detached,
at
which
point,
then
you
can't
really
use
it
like
you
should
anyway.
So
so
it's
gonna,
it's
gonna,
enable
some
performance,
but
also
as
we
move
forward
just
to
edit
the
files,
especially
with
typography
like
Dan
alluded
to.
These
are
extra
sections
where
we
would
maybe
show
some
false
positives
on
type
or
or
font
changes
that
haven't
been
made.
Eliminating
this
really
helps
streamline
some
of
the
process,
and
so
the
current
version.
A
There
is
still
a
deprecated
section
as
a
placeholder,
but
there
is
nothing
under
it.
Currently,
so
everything's
been
deprecated
and
we've
gone
through
that,
so
that
will
be.
That
will
be
very
helpful
again
if
you
need
access
to
any
of
that,
you
can
access
that
by
going
to
the
the
component.
Library
itself
click
the
drop
down
and,
in
this
case,
I'm
viewing
the
the
history.
A
But
you
can
choose
to
show
the
version
history
and
we
do
label
the
different
history
instances.
So
you
can
see
deprecations
throughout
here
where
those
branches
have
been
merged,
so
you
would
be
able
to
go
back
to
an
older
time
period
and
and
find
those
presents
in
there
should
you
need
them.
I
think
we've
kind
of
rounded
that
that
out
for
everybody,
where
there's
links
to
the
new
ones
and
you
can
still
access
the
old,
so
nice.
B
Just
a
reminder
to
let
us
know
if
these
updates
are
useful
and
if
there's
anything
missing
and
I
know
everything's
busy
and
not
not
a
lot
of
people
have
no
one's
got
any
spare
capacity,
but
if
there's
anything,
that's
really
missing
and
could
speed
up
your
workflows.
Please
do
let
us
know
with
trying
to
balance
everything
and
prioritize
things,
but
other
than
that
have
a
great
day,
foreign.