Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
thealscott authored Aug 29, 2024
1 parent 3b67952 commit 349f975
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ npm install github:yunojuno/figma-tokens#<release-version> --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#<release-version>`.

0 comments on commit 349f975

Please sign in to comment.