Changes to library but we didn't do anything

Hi ​@Mark_Steinruck 

Thanks for flagging. I can definitely see how getting unexpected notifications could be a bit unsettling. Would you mind submitting a bug report by following this article: https://help.figma.com/hc/en-us/articles/360041468234-Submit-a-bug-report? That way, our support team can take a closer look and get to the bottom of what's happening

Thanks for your patience.

Toku

Hi ​@Mark_Steinruck has this issue been resolved to you? Im building design system and i have the same problem, it feels very strange. Even on other files i get notified to publish something that i changed like 10 days ago but already have published multiple times in the meantime.

Hey ​@Mihailo Jancic, no it’s still doing the same thing as before. It wouldn’t bother me so much if there was some type of log indicating what changed, but it’s completely obscure and continues to happen without warning. 

Hello ! I have the same problem too. In the library file, Figma proposes to publish changes in components that haven’t been modified by anyone. 

Set apart the bug itself, it would be great to have, when you publish the library, a quick resume about what has changed in the component. The same we have in the project files, when we update the components based on the last library publication. It would be useful to review the component modification one last time before publishing.

Hi! Same issue here. Any fix?

Just switched from AdobeXD to Figma, bought the UntitledUI Kit and have the same problem :-(.
Published the UntitledUI LITE Kit and as soon as it’s done it already tells me I need to publish 450 changes.

Obviously I didn´t change a thing.
Fresh desktop install, fresh UI Kit and it behaves very strange (at least from a newby perspective)

Hi ​@Stefan HM!

Thanks for your reply - I can see how that is confusing for you. This was a known bug and our engineers pushed out a fix earlier today so it should be fully resolved soon. Please refresh your tabs and let us know if you still see this happening. If you do, please share your impacted file(s) with support-share@figma.com and grant "Can View" access, and we can flag this to the team. 

If you have any other questions let me know!

Is this fix live for everyone? My team and I are still running into this issue.

Thanks for your reply, ​@Jes Chuhta! I’m sorry to hear you ran into this. 

I want to clarify this a bit more with you so I know if it’s the same issue or a slightly similar one. Have you tried publishing the changes, and if you do, are you still seeing the same changes listed for publishing again? The fix should be live for everyone, so the same issue shouldn’t be affecting you.

One other thing to note is is how Figma treats core primitives. When an asset like a variable, style, or low-level component is modified, anything that depends on it (even transitively) is considered changed. Because of that, it can result in many updates appearing and becoming eligible for republishing. In more complex systems, it can be more unexpected when these publish updates show up.
 

Generally speaking, it’s good practice to publish changes so everything is up-to-date, though I can definitely understand why you would be hesitant when you aren’t sure what those changes are.

Hi ​@adamsmasher,
The same issue is still happening for me and the rest of the team for months now.

The changes were made to a completely different atom component and are not related to any other atom components. No shared variables, styles, or other dependencies were modified.

However, unrelated components are still showing the "Publish changes" even though no changes were made to them. For example, if I update the Tabs atom component, components such as Button, Tooltip, and several others are also marked as requiring publication. This behavior is becoming quite frustrating.

I've tried every workaround I can think of, including:

• Reloading Figma tab
• Closing and reopening the file
• Restarting Figma before commit to “Publish changes”
• Making a small "fake" edit and republishing the affected components

Unfortunately, the issue still there.

Hi, ​@Yoki Tyas. I can see why this is frustrating, particularly after doing a lot of troubleshooting. 

Just to clarify, even after you publish all changes, you continue to keep seeing more changes to publish? I’ve created a ticket for you so our Technical Quality team can investigate, but I wanted to clarify that point as a separate issue in addition to the unexpected changes.

You should get an email shortly from me, and I recommend replying to that with any additional information. In particular, it would be helpful if you provide file links to your design file and library, along with sharing those with support-share@figma.com with view access (this won’t affect your billing). Thanks so much for your patience!

Thanks for the response ​@adamsmasher 

Yes, I've noticed that it mostly happens with the same components.
I received your email and will share more detailed information there.

​@adamsmasher I’m seeing the same thing. I’ve noticed it for some time now, very confusing and worrisome as (you know) we treat our Libraries with special care because unnecessary changes impact a LOT of teams/files.

Here’s steps to reproduce. I’m on version 126.6.9 on Mac Desktop, but have seen this for several prior versions/months.

• View Assets panel > “Book” icon / Manage Libraries — See that there is nothing needing publishing (no Modified’s, no Added’s)
• Create branch named “Alert”
• In the new branch, I can verify there is no changes needing to be merged — i.e. it’s still clean
• I create a new component
  • This is a brand new component, let’s say “Alert”
  • My new Alert component consumes my file’s type styles, color styles, and a singular component from this file (my base Icon component)
  • No other components consume my new Alert component
• I begin merging back my new Alert component
  • In “Review and merge changes” I see my expected changes just in my singular artboard and singular component and ⛔️ I see unexpected changes in “Other” (see notes below)
  • I go back to main branch
  • I go back to Alert branch (this is a workaround, see below) — now I only see my expected changes just in my singular artboard and singular component
  • I merge
• Merge completes, I’m back in my main branch
• I go to my Assets panel > “Book” icon / Manage Libraries to publish my new Alert component
  • Expected: I see my new component Alert ready to be published as “Added”
  • ⛔️ I see 14 other components as “Modified” — I didn’t change them, I didn’t alter them, I have no idea why these are needing re-publishing
  • I re-publish them all because I want to keep my library “clean”, but when consuming files pull in this new change it’s not obvious at all what has changed.

Problem #2 — Mystery Changes in “Other”
Mentioned above, but maybe it’s related. I see it’s worse when components use Slots, but it’s also when a component doesn’t use Slots.

• Go through normal branch process — create branch, go to new branch, see it’s still “clean”, create new component, begin merge
• Some times, version A
  • In “Review and merge changes” I see my expected changes and ⛔️ I see unexpected changes in “Other”
    • I have no idea where these are — they aren’t changes I made, I have no artboard, component, or item called “Other”
  • I go back to main branch
  • I go back to feature branch (this is a workaround that I’ve noticed sometimes removes these changes) — now I only see my expected changes just in my singular artboard and singular component
  • I merge, but ⛔️ lots of untouched things are “Modified”
• Other times, version B
  • In “Review and merge changes” I see my expected changes and ⛔️ I see unexpected changes in “Other”
  • I go back to main branch
  • I go back to feature branch trying my workaround — ⛔️ instead this time the changes in “Other” are different, no pattern as to why, but they’re still there and I can’t go to them
  • I merge because I have to, and as you might expect ⛔️ lots of untouched things are “Modified”

Happy to screenshare if that’s helpful to the Figma team

Thanks for the detailed breakdown of the issue, ​@JK_Ryan - I can definitely understand why it’s confusing and worrisome.

Since you provided a really thorough description (particularly in noting the “mystery changes in Other”), I created a ticket with our Technical Quality team and included all of this in with the ticket. You should get that via email from me shortly, and you’re welcome to reply to that with any file links or other information that seems relevant. One additional question - you mentioned seeing this with the desktop app. Do you see this with the browser, too? I’m not sure it makes a difference, but it’s good to know either way. Thank you, and thanks for your patience!