fix: Add v1.2.0 historical snapshot and bump version to 1.3.0

[MantisClone]

Summary

This PR fixes a botched 1.2.0 deployment and prepares for the 1.3.0 release.

Problem

The GitHub Release 1.2.0 was created on Nov 5, 2025, but it failed to deploy correctly because the version number in tokens/token-list.json was still set to 1.1.0 at the time of the release. This caused:

1. The deploy workflow to create a duplicate v1.1.0.json file instead of v1.2.0.json
2. The v1.2.0.json endpoint on GitHub Pages to return a 404
3. The latest.json to still point to version 1.1.0

Solution

1. Add versions/v1.2.0.json - Manually created from the 1.2.0 tag content with the correct version number. This historical snapshot will be included in the next deployment.

2. Bump version to 1.3.0 - Updated tokens/token-list.json to version 1.3.0 so the next release will deploy correctly.

Verification

After this PR is merged and release 1.3.0 is created:

• https://requestnetwork.github.io/request-token-list/v1.2.0.json will return the 1.2.0 token list
• https://requestnetwork.github.io/request-token-list/v1.3.0.json will return the 1.3.0 token list
• https://requestnetwork.github.io/request-token-list/latest.json will point to 1.3.0

Release Instructions

After merging this PR:

1. Go to GitHub Releases
2. Create a new release with tag 1.3.0
3. The deploy workflow will automatically publish all version files including the missing v1.2.0.json

Summary by CodeRabbit

• Chores
  • Updated token list version to reflect incremental changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version minor field incremented from 2 to 3 in the token list configuration file. No changes to token data, major version, or patch version.

Changes

Cohort / File(s)	Summary
Version bump tokens/token-list.json	Minor version incremented from 2 to 3

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify the version bump is intentional and follows project versioning conventions
• Confirm no unintended modifications to token data or other version fields

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly reflects the main changes: adding a v1.2.0 historical snapshot and bumping the version to 1.3.0, which matches the raw summary showing a version bump from 1.2.0 to 1.3.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/v1.2.0-snapshot-and-v1.3.0-bump

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0f65861 and 1d85656.

📒 Files selected for processing (1)

• tokens/token-list.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Agent

🔇 Additional comments (1)

tokens/token-list.json (1)

4-8: Version bump to 1.3.0 is correct. The minor version increment from 2 to 3 aligns perfectly with the PR objective and semantic versioning conventions. This sets up the next deployment to correctly publish /v1.3.0.json alongside the manually added v1.2.0.json snapshot.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR addresses a failed 1.2.0 deployment by adding the missing historical snapshot and bumping the version to 1.3.0. The original 1.2.0 release failed because the version in tokens/token-list.json wasn't updated before the release was created, causing the deploy workflow to create a duplicate v1.1.0.json instead of v1.2.0.json.

Key changes:

• Added versions/v1.2.0.json with correct version number and Nov 5, 2025 timestamp
• Bumped version in tokens/token-list.json from 1.2.0 to 1.3.0 to prepare for next release

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.