Shortcut to publish library and automatically update files

Can’t wait to have this!

Pleeeeease add this! I spend so much of my day publishing and updating.

I really wish we could opt-in to auto-updates from specific libraries for specific files.

We have lots of design files that are on “maintenance mode”. They are required for occasional reference and should reflect our latest design system version, but they are not in active build or testing.

It would save so much time for designers during quarterly maintenance cycles for our artifacts. It’d be better for us to receive a cue that auto-updates have been applied, instead of waiting for a designer to enter the file in order to apply them. In the rare instance an auto-update caused a breaking change we could roll it back in version history.

The risk of a breaking change is low because we have a great design systems team. We spend the time on a great design system and standards for implementation to minimize risk during updates, so we shouldn’t have to spend more time making manual updates to each file (especially low-priority ones) when an update is published.

We really need this feature or at least a plugin!

+1. A feature/shortcut to quick-publish your library and a setting for files to auto-update (as I understand you don’t want certain files to update) would save so much time.

So irritating. It’s a super quick fix, guys.

still no sign on this 😦

Так и не решили вопрос(

A MUST HAVE!!!

Just.. Please. 😓

+1!!!

+1 — as the sole Product Designer across 4 applications, my focus is entirely on maintaining the design system and creating net new UX. It’s incredibly cumbersome and a huge time drain to spend hours navigating into files to accept design system changes just to maintain all of our hundreds of files.

I get why this workflow is in place for large design orgs, but the workflow needs of small design teams or teams of 1-2 is being completely overlooked here.

Currently building a design system in a new company and its a pain that this doesnt exist.

Yes, it requires responsibility, but you can prevent this easily:

• Just dont worry in single seat situations
• Warn the user when publishing by shortcut if the library is used in a specific amount of files
• Give an option on the other side when adding a library to collect or not collect auto updates or to maintain it as is with a manual prcoess from whoever is using your library

I did it, soon a link with the solution.

Just commenting to say that I need to be able to force-push certain updates - I keep seeing the same problems coming back because people don’t want to go back and update old files, but in the same breath will copy/paste from them as a shortcut to manually inserting components and tweak things, and then forget to update libraries. It causes a lot of confusion with the dev team. If I can’t automatically update files, I want to be able to prevent a designer from dismissing library updates or proceeding further with work on certain updates until they actually do the update.