tokens-bruecke 3.6.0 → 3.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,15 @@
1
+ ## [3.6.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.5.0...v3.6.0) (2026-08-21)
2
+
3
+ ### Features
4
+
5
+ - **cli:** add an interactive `init` command ([7752a58](https://github.com/tokens-bruecke/figma-plugin/commit/7752a580f14461dde5027ccb30573638ae4d5609))
6
+ - **cli:** keyboard navigation for the init prompts ([4a839bc](https://github.com/tokens-bruecke/figma-plugin/commit/4a839bc07fae8acd77a08d38edf320a75c4c480f))
7
+
8
+ ### Bug Fixes
9
+
10
+ - **ci:** generate the release CHANGELOG section that -r 1 silently skipped ([e116963](https://github.com/tokens-bruecke/figma-plugin/commit/e116963d0ceb82a738635bf15b627c0a5a5df956))
11
+ - **ci:** publish to npm via trusted publishing (OIDC) ([3775e31](https://github.com/tokens-bruecke/figma-plugin/commit/3775e31744e33f7442d143ebf36dfe4e13403301))
12
+
1
13
  # Changelog
2
14
 
3
15
  ## [3.5.0](https://github.com/tokens-bruecke/figma-plugin/compare/v3.4.4...v3.5.0) (2026-08-21)
package/README.md CHANGED
@@ -283,6 +283,7 @@ Is `off` by default. When enabled, each Figma variable collection is exported as
283
283
 
284
284
  - **Download JSON** — produces a `design.tokens.zip` archive containing one `{CollectionName}.tokens.json` per collection.
285
285
  - **CLI** — writes individual `{CollectionName}.tokens.json` files into the directory specified by `--output`.
286
+ - **Push to a server** — the GitHub, GitHub PR and GitLab servers commit one `{CollectionName}.tokens.json` per collection in a single commit. The `File name` field of the server becomes the folder they are written into, e.g. `tokens` → `tokens/{CollectionName}.tokens.json`.
286
287
 
287
288
  This is useful when you want to keep component-level token files separate (e.g. `button.tokens.json`, `card.tokens.json`).
288
289
 
@@ -292,6 +293,7 @@ Is `off` by default. When enabled, each mode of a variable collection is exporte
292
293
 
293
294
  - **Download JSON** — produces a `design.tokens.zip` archive containing one `{CollectionName}/{ModeName}.tokens.json` per mode.
294
295
  - **CLI** — writes individual `{CollectionName}/{ModeName}.tokens.json` files into the directory specified by `--output`.
296
+ - **Push to a server** — the GitHub, GitHub PR and GitLab servers commit one `{CollectionName}/{ModeName}.tokens.json` per mode in a single commit, inside the folder set in the server's `File name` field.
295
297
 
296
298
  Collections with a single mode are exported as a single `{CollectionName}.tokens.json` file.
297
299
 
@@ -670,6 +672,8 @@ In ordere to test if your credentials are valid you can make a test request by c
670
672
  4. In the file name field you can specify a path to the file. If the file doesn't exist, it will be created. If the file exists, it will be overwritten. File name should include the file extension, e.g. `tokens.json`.
671
673
  5. You can also specify a commit message.
672
674
 
675
+ > **Splitting into several files.** If _Split collections into separate files_ or _Split modes into separate files_ is enabled in the advanced settings, the file name field is treated as a folder instead, and every file is written in a single commit — e.g. `tokens` → `tokens/Colors.tokens.json`, or `tokens/Colors/Light.tokens.json` when splitting by mode.
676
+
673
677
  ![fig.8](readme-assets/fig8.webp)
674
678
 
675
679
  ### [GitHub PR](https://github.com)
@@ -686,7 +690,10 @@ All the steps are the same as for the [GitHub](#github) server, except the last
686
690
  1. You need to create a [project access token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html) with `api` scope.
687
691
  2. In the plugin settings paste the token into the `Project access token` field.
688
692
  3. Add an owner name, repository name and a branch name.
689
- 4. In the file name field you can specify a path to the file. If the file doesn't exist, it will be created. If the file exists, it will be overwritten. File name should include the file extension, e.g. `tokens.json`. 5. You can also specify a commit message.
693
+ 4. In the file name field you can specify a path to the file. If the file doesn't exist, it will be created. If the file exists, it will be overwritten. File name should include the file extension, e.g. `tokens.json`.
694
+ 5. You can also specify a commit message.
695
+
696
+ > **Splitting into several files.** If _Split collections into separate files_ or _Split modes into separate files_ is enabled in the advanced settings, the file name field is treated as a folder instead, and every file is written in a single commit — e.g. `tokens` → `tokens/Colors.tokens.json`, or `tokens/Colors/Light.tokens.json` when splitting by mode.
690
697
 
691
698
  ![fig.11](readme-assets/fig11.webp)
692
699