Skip to main content
Fernanda_Ruiz
September 1, 2021

Shortcut to publish library and automatically update files

  • September 1, 2021
  • 96 replies
  • 14434 views

My team and I are currently having the inconvenience of having to publish our library every single time we make even a small change (like a font size increase, color change, etc.) and then switching to the working file and manually updating the library. Due to the nature of the project we do this quite frequently and having to publish – switch file – update every single time to see the changes in our designs turns out very time consuming if you add it up.

It would be amazing if Figma could integrate a shortcut for automatically updating a library and automatically updating the files it is being used on (like a cmmd+S shortcut!), of course not everybody might want to have this so it would also be nice to be able to turn this shortcut on and off.

96 replies

Chris_Johnston
September 5, 2021

This is bugging me too. I can see thee value is huge organizations but for a small shop wanting to do things right, its a waste of time. Wish I could select autopublish. Thanks!

Melissa_Samworth
October 2, 2021

Yes I could not agree more! I am actually the only designer on my team, but I like to centralize my design system. So I’m constantly publishing updates to myself, and going through this whole process! Haha. It is annoying.

November 1, 2021

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

StLa
December 3, 2021
  1. Right now the publication flow is very long and heavy, even for small updates.
  1. Alt+3, 2) Publish 3) Publish 4) Switch file 5) Review 6) Update
  1. A solution would be to offer a “Quick Publish” option for files.
    Hit Alt+Maj+3, everything is published, and files that depend on the library update automatically.
Devin_Schvaneveldt
December 7, 2021

Autopublish please 🙏

Travis2
Active Member
December 8, 2021

Designers will hunt you down the first time you force-push an update that breaks their overrides.

What I would love to see, because it’s risk-free, is the ability to force-push updates to component descriptions. Sometimes it’s helpful to edit your instructions or to insert new keywords, but getting designers to accept updates on a component - even when it’s literally no risk to their designs - can be difficult.

Fernanda_Ruiz
December 8, 2021

That’s why I proposed this feature to be optional for a team project because not everybody would like to open their files and see things changed

Dee_Arvanitis
December 16, 2021

This should be optional on a per-user basis. We have a complex app and it’s maddening to do this from tens to dozens of times per day. Not expected in a power tool.

Sam33
December 20, 2021

Also agree! The workflow is too long. I need a way to auto-publish library changes and have those changes be automatically reflected in the file i’m using the library in.

Adam
December 20, 2021

Users don’t get updated, files do. So it would likely have to be a per-file basis.