Skip to main content
Solved

Publish library: description of changes

Greg_Smith

figma-publish

When I’m publishing a library, do I have to detail all of the changes (indicated by the list shown in the pop-up, with items that I can check/un-check) in the “Optional description of changes,” or will all those items that were changed be shown somewhere else, to users, when they look for a changelog of some kind?

In other words, if I’m publishing changes to multiple components, but I leave the “Optional description of changes” empty, will those changes be shown somewhere, in a publish history? Change-log? etc.?

Seems a bit dumb to to enter into that field everything that’s listed below it. 🤔

Best answer by Josh

Hey @Greg_Smith, great question. Yup after publishing users will get a notification that the library has been updated. Within that notification they can review the changes which will show the list of updated styles and components along with the description if provided.

Here’s our help article that outlines this. Hope this helps! 😊

View original
Hannah_West_Drake
Marine_Kambara1
2 people like this
  • Hannah_West_Drake
    Hannah_West_Drake
  • Marine_Kambara1
    Marine_Kambara1
This topic has been closed for comments

3 replies

Josh
  • Josh
  • Former Community Manager
  • 1019 replies
  • Answer
  • June 15, 2021

Hey @Greg_Smith, great question. Yup after publishing users will get a notification that the library has been updated. Within that notification they can review the changes which will show the list of updated styles and components along with the description if provided.

Here’s our help article that outlines this. Hope this helps! 😊

Greg_Smith
1 person likes this
  • Greg_Smith
    Greg_Smith
Greg_Smith
  • Greg_Smith
  • Author
  • New Member
  • 11 replies
  • June 15, 2021

Thank you, Josh!

Josh
1 person likes this
  • Josh
    Josh
Rob_Brogan1

I know this is an old post but that’s kind of an incomplete answer. The ONLY people seeing that pop-up with list of changes is the first designer to open a file and accept the changes. When a second designer comes in, they would have no idea at all. Or in my case the difficulty is mostly with developers. Anyone building out your designs will also not see that notification.

It is also not stored or tracked anywhere after the fact. Once you accept updates on the file, poof. So you need to be diligent with writing detailed descriptions of which components were changed and what you changed about them so that the developers can stay in sync with you creating style changes that aren’t in the front-end system.

I was looking for a plugin or tool to save some time on doing this and that’s how I got here 😉

It would be so nice if everyone could get a little digest like:

  • primary button, secondary button changed:

border radius 4 → 8

  • secondary button changed

fill color grey → black
…etc.

Julien_Galster1
cporten
Jack Zwanenburg
3 people like this
  • Julien_Galster1
    Julien_Galster1
  • cporten
    cporten
  • Jack Zwanenburg
    Jack Zwanenburg
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings