[#1053] Update test-mode milestones to current prod values#1054
Merged
realproject7 merged 1 commit intomainfrom May 5, 2026
Merged
[#1053] Update test-mode milestones to current prod values#1054realproject7 merged 1 commit intomainfrom
realproject7 merged 1 commit intomainfrom
Conversation
TEST_CONFIG.MILESTONES were stale ($7K/$10K/$35K/$50K) and showing publicly because Vercel runs with NEXT_PUBLIC_AIRDROP_MODE=test. Update to match the canonical values in PROD_CONFIG and the "How does this work?" modal copy: $1M/$10M/$50M/$100M. Campaign dates and pool amount in TEST_CONFIG remain unchanged (only the milestone values were flagged as stale). Fixes #1053 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1053
Summary
TEST_CONFIG.MILESTONESinlib/airdrop/config.tswere stale ($7K/$10K/$35K/$50K) and were rendering on https://plotlink.xyz/airdrop because the Vercel deployment runs withNEXT_PUBLIC_AIRDROP_MODE=test. Updated to match the canonical $1M/$10M/$50M/$100M values that already exist inPROD_CONFIGand the "How does this work?" modal copy.CAMPAIGN_START/CAMPAIGN_END/POOL_AMOUNTinTEST_CONFIGare intentionally unchanged — the user only flagged the milestone values as stale.Files
lib/airdrop/config.ts—TEST_CONFIG.MILESTONESonly (4 lines)package.json— version 1.6.2 → 1.6.3 (3rd digit, bug fix)Test plan
npm run typecheckpassesnpm run lintpasses (no new warnings onconfig.ts)Coordination note
Only
lib/airdrop/config.tsreferences the old7_000/35_000literals (verified via grep) — no other files needed touching.