@synergy-design-system/assets 1.0.2 → 1.1.0

package/CHANGELOG.md

@@ -1,3 +1,10 @@
+# [@synergy-design-system/assets-v1.1.0](https://github.com/synergy-design-system/synergy-design-system/compare/assets/1.0.2...assets/1.1.0) (2024-01-12)
+
+
+### Features
+
+* ✨ add syn-tag ([#217](https://github.com/synergy-design-system/synergy-design-system/issues/217)) ([da91945](https://github.com/synergy-design-system/synergy-design-system/commit/da91945d1e7f4e5bb5cc2efd36e70f790c5663ad))
+
 # [@synergy-design-system/assets-v1.0.2](https://github.com/synergy-design-system/synergy-design-system/compare/assets/1.0.1...assets/1.0.2) (2023-12-14)
 
 

package/README.md

@@ -2,28 +2,31 @@
 
 This package is taking care about getting assets (like logos, system icons and default icons) from Figma.
 The folder structure of the assets corresponds to the structure of the Figma page.
- - **logos:** contains the variants of the SICK brand logo
- - **icons:** contains the standard icons based on [Material Icons](https://fonts.google.com/icons)
- - **system-icons:** contains a small subset of icons, that are internally used by the Synergy components
 
-> **Note:** All assets from figma, which should not appear in this package (e.g. documentation), will start with an underscore (e.g. _my-doc-for-an-asset). This assets are getting filtered and ignored by this package.
+- **logos:** contains the variants of the SICK brand logo
+- **icons:** contains the standard icons based on [Material Icons](https://fonts.google.com/icons)
+- **system-icons:** contains a small subset of icons, that are internally used by the Synergy components
+
+> **Note:** All assets from figma, which should not appear in this package (e.g. documentation), will start with an underscore (e.g. \_my-doc-for-an-asset). This assets are getting filtered and ignored by this package.
 
 ### Setup
+
 To update the assets from Figma, first of all a personal access token in Figma needs to be created.
 The documentation how this can be achieved can be found [here](https://www.figma.com/developers/api#access-tokens).
 The only needed scope is "File content" set to readonly.
 
-After the creation of the personal access token, it needs to be saved in a ***.env*** file with the variable ***"FIGMA_PERSONAL_ACCESS_TOKEN"***.
-It should look like following: 
+After the creation of the personal access token, it needs to be saved in a **_.env_** file with the variable **_"FIGMA_PERSONAL_ACCESS_TOKEN"_**.
+It should look like following:
 
 ```
 FIGMA_PERSONAL_ACCESS_TOKEN = "my-personal-access-token"
 ```
 
 ### Update assets from Figma
+
 If something in the Figma assets got changed, the assets of this package also needs to be updated.
 To update the assets run following in the terminal of the assets package folder:
+
 ```
 pnpm fetch-assets
 ```
-

package/package.json

@@ -104,10 +104,12 @@
     ]
   },
   "type": "module",
-  "version": "1.0.2",
+  "version": "1.1.0",
   "scripts": {
     "lint": "eslint .",
+    "format.eslint": "pnpm lint --fix",
     "fetch-assets": "node scripts/fetch-assets.js",
-    "release": "semantic-release  --tagFormat 'assets/${version}' -e semantic-release-monorepo"
+    "release": "semantic-release  --tagFormat 'assets/${version}' -e semantic-release-monorepo",
+    "release.dry": "semantic-release --dry-run --tagFormat 'assets/${version}' -e semantic-release-monorepo"
   }
 }