Skip to main content
Question

Publishing Figma Make Kit from Github CI

  • April 15, 2026
  • 3 replies
  • 57 views

Aneta Nina Chodor-Kjeldsen

I’m publishing my Make kit package (@my-org/figma-make-kit) to Figma’s npm registry from GitHub CI (currently 2.0.0), but when a user in our Org creats a new Make files using our Kit, Figma Make still pull the older kit-published version (1.0.0).
When I try to update the kit in Figma via Edit items in kit + Update kit + Publish, Figma attempts to publish the package to Figma’s npm again and fails with “this package version already exists” and the Update kit modal also tries to bump the version (e.g., 2.0.1), which would then conflict with my CI publishing flow, as the next time we would try to publish from CI to Figma, we will get an error in CI “this package version already exists”.

Is it possible to automate publishing of Figma Make Kits from our own CI?
Why Figma Make is not able to consume the latest CI-published version to Figma’s npm registry without requiring Update kit to publish a new package version?

3 replies

  • Figmate
  • April 16, 2026

Hi ​@Aneta Nina Chodor-Kjeldsen

 

I understand your goal is to fully automate the publishing of your Make Kit from GitHub CI.

 

The core issue seems to be that you need to manually increment the version number to resolve the "this package version already exists" error when publishing updates, but this then conflicts with your CI's versioning.

I will pass your post along to our team for their review.

We will update this thread as soon as we have more information.

 

Thanks again for bringing this to our attention.


Aneta Nina Chodor-Kjeldsen

Hi ​@Junko3,

Yes, exactly.  We have already a number of skills & instructions files in our repo for AI agents (used by developers in their IDE), so would be great just to bring those into Figma Make Kit. 
95% of guidelines MD files are common in both use-cases, and we want to automate that, so we don’t have to manually copy them over to Figma Make Kit.

Thanks for looking into this.


  • Figmate
  • April 16, 2026

Thanks for confirming and sharing additional context! This has been shared internally as well. I'll keep you posted.