From cc2ab8f443d2332b286f325dcbe0ff399cbe5f52 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 13 Mar 2026 13:21:00 -0400 Subject: [PATCH 1/2] fix: correct tag format in README publish procedure Tags use `1.2.0` format (no `v` prefix), not `v1.2.0` as documented. The deployed files on GitHub Pages do use the `v` prefix (e.g., `v1.2.0.json`), but the git tags themselves do not. Co-Authored-By: Claude Opus 4.6 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 22b80dd..37805ca 100644 --- a/README.md +++ b/README.md @@ -82,8 +82,8 @@ We welcome community contributions! To add a new token to the list: After merging changes to `main`: -1. Create a GitHub Release with a tag matching the version in `tokens/token-list.json` (e.g., `v1.2.0`) - - The tag must use the format `v..` (e.g., `v1.2.0`) +1. Create a GitHub Release with a tag matching the version in `tokens/token-list.json` (e.g., `1.2.0`) + - The tag must use the format `..` (e.g., `1.2.0`) — no `v` prefix - Ensure the release tag matches the version in your token list exactly 2. The deployment workflow will automatically: - Update the timestamp to the current deployment time From 10080dbcdcaa35e794c9fc323006ec03bfb48c18 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 13 Mar 2026 13:22:48 -0400 Subject: [PATCH 2/2] fix: note that deployed files use v prefix but git tags do not Co-Authored-By: Claude Opus 4.6 --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 37805ca..650d471 100644 --- a/README.md +++ b/README.md @@ -93,6 +93,8 @@ After merging changes to `main`: Monitor deployment progress in the [Actions tab](https://github.com/RequestNetwork/request-token-list/actions/workflows/deploy.yml) of this repository. +**Note**: Git tags do not use a `v` prefix (e.g., `1.2.0`), but the deployed files on GitHub Pages do (e.g., `v1.2.0.json`). The `v` prefix is added by the deployment workflow automatically. + **Note**: The workflow does not validate that the release tag matches the version in `tokens/token-list.json`. If they don't match, the deployed version will use the version from the JSON file, not the release tag. Always ensure they match to avoid confusion. ## Development