Skip to content

chore: migrate using-tokens-from from S01-Issuer to st0x.registry#10

Merged
hardyjosh merged 1 commit into
mainfrom
chore/migrate-tokens-pin
Jun 1, 2026
Merged

chore: migrate using-tokens-from from S01-Issuer to st0x.registry#10
hardyjosh merged 1 commit into
mainfrom
chore/migrate-tokens-pin

Conversation

@hardyjosh

@hardyjosh hardyjosh commented May 31, 2026

Copy link
Copy Markdown
Contributor

S01-Issuer/st0x-tokens is the abandoned predecessor of the canonical
ST0x-Technology/st0x.registry token list. The pinned commit ad1a637
is from 2026-02-11 and is missing every token added since: wtQQQM,
wtVWO, wtARKK, plus the BMNR ticker correction in registry PR #20.

Pin to current st0x.registry/main (d4fcef4) instead. No new tokens
land here — that's a separate PR adding CEG/DRAM/TSM/SGOV to
config.toml. This is the source-of-truth migration only.

Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com

Summary by CodeRabbit

  • Chores
    • Updated the base token-list source to reference a newer upstream version.

`S01-Issuer/st0x-tokens` is the abandoned predecessor of the canonical
`ST0x-Technology/st0x.registry` token list. The pinned commit ad1a637
is from 2026-02-11 and is missing every token added since: wtQQQM,
wtVWO, wtARKK, plus the BMNR ticker correction in registry PR #20.

Pin to current `st0x.registry/main` (d4fcef4) instead. No new tokens
land here — that's a separate PR adding CEG/DRAM/TSM/SGOV to
config.toml. This is the source-of-truth migration only.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 31, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0ae07e93-c52e-4f7f-a8d2-e49875a8a24d

📥 Commits

Reviewing files that changed from the base of the PR and between 297a2e8 and 264601d.

📒 Files selected for processing (1)
  • strategy/settings.yaml

📝 Walkthrough

Walkthrough

The strategy configuration file was updated to use a new upstream source for token lists. The using-tokens-from URL now points to a different token-lists/base.json endpoint, replacing the previous st0xTokens source path.

Changes

Token List Configuration

Layer / File(s) Summary
Token source configuration update
strategy/settings.yaml
The using-tokens-from configuration value updated to reference a new upstream token-lists/base.json endpoint instead of the previous source.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🐰 A token list update so neat,
From old paths to fresh URLs we greet,
New lists now in place,
A configuration embrace,
The strategy's sources are sweet!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: migrating the token list source from S01-Issuer to st0x.registry, which is clearly demonstrated in the file change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/migrate-tokens-pin

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@hardyjosh hardyjosh merged commit 1c45a61 into main Jun 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant