From 349f975e6b2830edb703a32f7ae79c6032a668dd Mon Sep 17 00:00:00 2001 From: thealscott Date: Thu, 29 Aug 2024 08:33:14 +0100 Subject: [PATCH] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6c47b40..79d0849 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,8 @@ npm install github:yunojuno/figma-tokens# --save-dev ## Releasing a new version When you have got to a point where you want to make a new release do the following. 1. Ensure the tokens and build folder have been updated. This should have ran in the actions tab. See it [here](https://github.com/yunojuno/figma-tokens/actions). -2. Update the package.json "version" to reflect the new version. See it [here](https://github.com/yunojuno/figma-tokens/blob/ccea4e736edf5b718c9d19bfe233ffdb3632b87d/package.json#L3) +2. Update the package.json "version" to reflect the new version. See it [here](https://github.com/yunojuno/figma-tokens/main/package.json#L3) 3. Create a new release and tag which match the version in the package.json. Ensure "latest release" is checked. Do that [here](https://github.com/yunojuno/figma-tokens/releases/new). 4. Notify the dev team at #dev. + +NOTE: You will not see a new release propagate to platform environments until the dependency is updated. This can be done either as part of the normal weekly dependency updates process, or if you need the changes more immediately you can run `npm install @yunojuno/figma-tokens@github:yunojuno/figma-tokens#`.