diff --git a/CLAUDE.md b/CLAUDE.md index f637dd6..f0cadf3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -263,3 +263,4 @@ publish actions on shared state. Write the files, hand the user the commands. - The **last main commit** — `git log --first-parent main -1 --format='%ai %h %s'`. A comment after the last release but before a fix on main may already be addressed there but unreleased. - The **current branch's tip** — your own unmerged work obviously can't be what the comment is reacting to. Always disambiguate "released," "merged-but-unreleased," and "in-progress" before agreeing that a user-reported problem is unfixed (or that a fix is incomplete). A user saying "your fix only covers X" about a recent PR is usually pointing at the *released* shortcomings — your in-flight branch may already address them but they have no way to know that. +- **Version-tag every image referenced in `README.md`.** GitHub caches README images (`raw.githubusercontent.com` with a 5-minute TTL; third-party hosts sit behind the long-lived camo proxy), so updating an asset in place can keep showing the stale version. Give each README image URL a `?v=N` query tag and **bump `N` in the same commit whenever the asset bytes change** — e.g. `assets/waitlist.svg?v=2`. The changed URL sidesteps every cache so the new image shows immediately instead of waiting on a TTL to expire. diff --git a/README.md b/README.md index b9ba4f6..250b507 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ **The CodeGraph platform is coming** — for every PR, know exactly what to test, what could break, which flows are affected, and whether business logic is compromised. -Join the waitlist for early beta access +Join the waitlist for early beta access Get early beta access to the hosted product · getcodegraph.com diff --git a/assets/waitlist.svg b/assets/waitlist.svg index 36dea5d..04d9bac 100644 --- a/assets/waitlist.svg +++ b/assets/waitlist.svg @@ -1,6 +1,6 @@ - - Join the waitlist! - + + Join the waitlist + @@ -13,10 +13,10 @@ - + - - + +