Skip to content

docs: use stable Amplitude logo URL - #79

Merged
aliaksandr-kazarez merged 1 commit into
mainfrom
codex/sdk-353-stable-logo
Oct 8, 2026
Merged

aliaksandr-kazarez merged 1 commit into
mainfrom
codex/sdk-353-stable-logo

Conversation

@aliaksandr-kazarez

@aliaksandr-kazarez aliaksandr-kazarez commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Replace the deployment-specific logo asset URL with the stable Amplitude brand URL in documentation. This prevents README images from depending on retention of an old application build.

Related: SDK-353.

Validation

  • Verified every changed file is byte-for-byte identical except for the exact logo URL substitution.
  • git diff --check passed.
  • Runtime tests not run; only documentation image URLs changed.

Checklist

  • Does your PR title have the correct title format?
  • Does your PR have a breaking change?: No; documentation-only URL replacement.

Prepared with Codex. LLMs make mistakes — please verify before acting.


Note

Low Risk
Single README image URL change with no code, auth, or data handling impact.

Overview
Updates the README header image to use https://static.amplitude.com/brand/amplitude-logo-with-text.svg instead of a lightning build-specific static asset path, so the logo does not break if that old deployment artifact is removed.

Documentation-only; no SDK or runtime behavior changes.

Reviewed by Cursor Bugbot for commit f9bd7ba. Bugbot is set up for automated code reviews on this repo. Configure here.

@linear-code

linear-code Bot commented Oct 8, 2026

Copy link
Copy Markdown

SDK-353

@aliaksandr-kazarez
aliaksandr-kazarez marked this pull request as ready for review October 8, 2026 17:14
@aliaksandr-kazarez
aliaksandr-kazarez merged commit 6e7460b into main Oct 8, 2026
13 checks passed
@aliaksandr-kazarez
aliaksandr-kazarez deleted the codex/sdk-353-stable-logo branch October 8, 2026 21:16
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.

3 participants