fix: use absolute image URLs in README so they render on the registry - #20
Merged
Conversation
README's header logo/plus-icon and screenshot-gallery images used repo-relative src paths. GitHub auto-resolves those against the repo's raw-content base, so they rendered fine there -- but the Tabularium registry serves the README's HTML standalone with no such resolution, so all 6 images 404'd on the plugin's actual registry page once the README finally synced. Switched to absolute raw.githubusercontent.com URLs, matching the pattern already used for postgresql-icon.svg and the .tabularium screenshots array.
aesslinger
added
the
prerelease:beta
Version suggestionBased on this PR's title (
This is informational only — no tag or release is created automatically yet. |
aesslinger
added a commit
that referenced
this pull request
Aug 14, 2026
Continuation of the beta line after PR #20 (absolute image URLs in README, fixing broken images on the Tabularium registry page) and the carried-forward PR #19 description rewrite. Registry-listed release. Verified: .tabularium re-validated clean against the live registry schema; cargo build/test (85/85)/clippy/fmt all pass; markdownlint clean.
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.
Summary
README's header logo/plus-icon and screenshot-gallery images used repo-relative
srcpaths (assets/plus.svg,assets/screenshots/*.png). GitHub auto-resolves relative image paths against the repo's raw-content base, so they rendered correctly there — but the Tabularium registry serves the README's rendered HTML standalone, with no such resolution. Once the registry's README sync finally caught up (confirmed today,readmeHtmlis now populated on/plugins/postgresql), all 6 images 404'd on the actual published plugin page.Switched all 6 to absolute
raw.githubusercontent.comURLs, matching the pattern already used forpostgresql-icon.svg(in the header, already absolute) and the.tabulariumscreenshotsarray (already absolute, which is why those never had this problem).Verification
npx markdownlint-cli README.md CHANGELOG.md→ cleansrc="assets/...relative paths in the README.tabulariumTest plan