Follow new updates and improvements to Tokens Studio.
January 17th, 2025
Fixed a few issues related to sync providers as well as some issues around import and application of tokens.
Fixed an issue in gitlab sync, where when a user is trying to load tokens in a repo, the "Initial Commit" message is causing an error because the commit message is not in line with the user's company's commit message rules - for those folder creations we now use the same commit message as entered
Fixed an issue related to applying paragraph indent tokens
When importing variables and they use decimals, we fixed an issue with decimals sometimes appearing with too many decimals due to a Figma issue in #3241
Fixed an issue where users were able to create empty token groups by .
values in #3245
Fixed an issue with GitLab’s .gitkeep files in #3199
Tokens Studio platform sync: Fixed $theme metadata in #3243
Tokens Studio platform sync: Increased limit for tokens sets, you should run into less issues now
December 23rd, 2024
8cbef62: Improved Tokens Studio Sync provider creation to work with our new API backend - you now no longer need Connection ID and urn, but just require an API key which will then let you pick organization and project. Note if you had existing sync providers set up with this provider you might need to edit them to use the right project.
December 9th, 2024
Fixes an issue with variables when updating a token's value from a reference to a hard value (e.g. #ff0000), the check we introduced in the last release caused those to not be updated (and only worked when changing to another reference).
November 27th, 2024
A small release this time that fixes an annoying issue with Bitbucket sync 😬
23caccd: Fixes sync with Bitbucket provider:
Pull when the option is to sync with a single file was not working
Push was removing all other .json files in the selected folder (either root of the chosen folder)
November 21st, 2024
04f3fa6: When updating variables we now properly check if the variable needs to be updated, which fixes an issue where Figma was showing library updates even though the values were the same
1af628f: fixed an issue with pulling token sets from Bitbucket when multi-file sync is enabled, wherein all the token sets were not being pulled.
fdfc7be: Fixed an issue related to cache for Bitbucket - caching is now disabled
October 24th, 2024
da1886d: Re-introduces "Update Figma Styles on Apply" (disabled by default). If enabled, the plugin will update any local styles when you apply or when themes change. By default, this setting is off. It's available from the gear menu in the bottom right. Note: This will update all styles in the document, which sometimes might be unexpected for some users
80a5a92: Fixed an issue where sometimes duplicate sync providers would show up
4fd3f9b: Fixed an issue where updating variables sometimes updated their description if both were empty
7be0b29: Fixed an issue where referencing a gradient would result in an empty color style; now the style correctly resolves to the gradient.
a6eb07d: Fixes a bug where applying a typography token to a text node would override individual property changes (like font size or font family) when "Apply to selection/page/document" is clicked.
September 25th, 2024
This release comes with a few bugfixes around themes and sync providers as well as a fix for a variable issue due to a bug in Figma’s Variables API that caused wrong variables to be applied or used as references.
Fixed an issue introduced in 2.1.0 that sometimes caused the order of token sets to not be as expected, meaning sets that acted as overrides didn't correctly get calculated.
Resolved an issue with Bitbucket sync where deleted sets were still being reflected in the tokens repository.
Fixed a bug where applying themes using "Prefix styles with active theme name" didn't correctly apply the right styles.
Fixed an issue with "zombie variables". Basically, even though a Figma file shows 0 variables, Figma's plugin API will sometimes tell us there's variables existing - probably ones that existed in the past but should be deleted - Figma seems to report those as existing still. This led to issues around applying and referencing variables where we'd point to those zombies. We now correctly check if the variable's collection still exist, and only then use those as references.
September 11th, 2024
😍 Theming is less strict again
We heard your feedback on theming and creating styles. 2.0 made theming much stricter, where you had to have token sets defined as references for each and every theme. We now optimized this to be more forgiving. Basically, if you export themes and you are exporting multiple themes at once, we now look at the overall configuration of token sets and pass these on as tokens to use for resolution. Meaning, you should not run into issues where you have broken references anymore just because a token set was disabled in on theme configuration even though you needed it. We now treat non-enabled sets as sources still - but they come last meaning enabled or source sets will always win. - 0bc599e
🐛 Fixes around style and variable creation
Fixes issue where styles are not applied in Figma, when user creates styles based on Token Sets - e1838a3
Fixed an issue around style creation where if numerical weights were used inside a created variable we'd display an error that we're unable to apply the font. We now changed this to properly load all weights of the font family and then create styles correctly with variable references to the numerical weight variable. You should be seeing 'Unable to apply font/weight combination' much less. - 087b4c1
Changed logic when "Remove styles and variables without connection to a token" is enabled where we now look at all created tokens in this session and remove those that should be removed, instead of looking at each theme individually and removing those that weren't created. You should be able to turn this on and it wont remove styles by accident. - 2c60963
Fixes style creation if color token was using a modifier and using a reference. We now correctly create a raw hex value as Figma doesn't have modifiers. Before we falsely used a reference without the modifier applied leading to styles that had a reference variable even though it should've respected the modifier - 087b4c1
Optimized the speed of importing variables. Importing should now feel drastically faster. If you're using Tokens Studio platform sync (Alpha), import variables will currently not work - we're bringing this back soon. - 8f97ea6
🐛 Other bugfixes and changes
August 30th, 2024
Fixes an issue where applied styles are not displaying in Figma, when the themes have been exported as non-prefixed styles from the plugin. https://github.com/tokens-studio/figma-plugin/issues/3095
Fixes the issue where applied styles are not displaying in Figma, when the themes have been exported with both 'prefix styles with active theme name' and 'ignore first part of token name for styles' options checked. https://github.com/tokens-studio/figma-plugin/issues/3088
August 28th, 2024
Fixes issues when synchronizing data with GitLab, which prevented creating new branches on the fly and switching between single and multi-file setups. https://github.com/tokens-studio/figma-plugin/issues/3076
Fixes the issue where only active themes were being exported as styles, even when multiple themes were selected in the options modal. https://github.com/tokens-studio/figma-plugin/issues/3088
Fixes the problem where applied styles were not being displayed in figma when the core/global theme was being activated https://github.com/tokens-studio/figma-plugin/issues/3083
Fixes a visual bug in the Resolve Duplicate Tokens modal https://github.com/tokens-studio/figma-plugin/issues/3068