Repository navigation
feat: changelog backfill from 2025 - #123
Merged
Merged
Conversation
Add 45 text-only entries covering March 2025 to September 13, 2026: one entry per feature a user would notice and one Improvements digest per month. Fix three live entries against git: partner-profile-settings (date 2026-04-03, real tabs and payout methods), invite-partners (2026-07-04 PT) and blog-launch (2026-07-05 PT). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… entries Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Review round 1 and a claim-by-claim check of all 44 new entries: drop features that were admin-only, hidden or never shipped, correct reward, pricing and tracking mechanics, and move dates to the PT day each change reached production. Fold the March 2025 digest into the launch entry. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Every entry now uses the PT day it reached production (Vercel production deploy, CMS release tag or npm publish). Drop the CLI setup stripe flow that never completed, and word retired features in the past tense. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
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
1 participant
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.
What
Backfills affitor.com/changelog from Affitor's start (March 2025) to September 13, 2026, where the weekly digests begin. 44 new entries, all text-only in the style of OpenAI's changelog (date, title, short paragraph, bullets, links). No banners and no images: none of the older screens can be shown truthfully with today's product.
Also fixes three live entries against git:
partner-profile-settings: date 2026-04-03 (was 04-10); the tabs were Account, Payout and Privacy & Security, and payout methods were bank transfer, Wise and PayPal (the entry said Stripe; there was none).invite-partners: 2026-07-04 PT (CMS v3.16.0 tag 20:51 PT, dashboard main 21:11 PT).blog-launch: 2026-07-05 PT (affitor.com/blog live 17:23 PT; 12 posts by 19:25 PT).Round 3: every entry is re-dated from production events (READY Vercel production deploys of the dashboard and docs, CMS release tags, npm publish times), and every sentence that names a command, button, page or money was re-checked, including whether it still exists today.
Round 2: every claim in every new entry was checked against the code at its date (user-facing page plus API route; admin-only, staging-only, hidden or demo-data features removed), and every date was moved to the PT day the change reached production (CMS release tag, or merge to
main; 2025 dashboard work dated by the uat→main release merge).Entries per month
Two entries are
type: pricingand need an explicit ok before publishing: paid-plans-2025 and pricing-2026.Sources (production date, all PT)
2025 dashboard PR numbers came from an older fork and do not match today's repo, so 2025 rows cite commit SHAs.
Left out on purpose
login,programs,whoamiin April 2026setup stripe(2026-04)Checks
/docs/...link points to an existing page; dashboard pages linked with absolute URLs.🤖 Generated with Claude Code