Skip to content

feat(bluesky): support 5–10-image gallery embeds - #515

Draft
bmwelby wants to merge 3 commits into
getopenpost:mainfrom
bmwelby:feat/bluesky-gallery-5-to-10-images-20261112
Draft

bmwelby wants to merge 3 commits into
getopenpost:mainfrom
bmwelby:feat/bluesky-gallery-5-to-10-images-20261112

Conversation

@bmwelby

@bmwelby bmwelby commented Nov 20, 2026

Copy link
Copy Markdown

Summary

Add Bluesky image galleries for 5–10 images per post or thread segment, preserving the existing app.bsky.embed.images record for 1–4 images. The backend emits app.bsky.embed.gallery for larger image sets, preserving image order, alt text, blob references and aspect ratios. The server capability catalogue and frontend validation now expose the ten-image limit.

Includes regression tests, an updated media-limits guide and Bluesky provider reference, and the required changes/bluesky-gallery.md fragment.

Motivation

OpenPost currently prevents authors from selecting more than four Bluesky images. Supporting gallery embeds lets authors publish multi-slide posts without splitting content or losing image descriptions.

Testing

  • Backend tests pass (go test ./...) — full backend PASS with OpenPost's supported dev build tag: go test -tags dev -p 1 -count=1 -timeout 30m ./... (isolated Railway SUCCESS 0916b7d4-a027-4fcb-8a56-2916d1a2d0b0). Untagged go test ./... requires generated frontend embed assets not present in the Go-only QA image.
  • Frontend tests pass (bun run --filter @openpost/web test) — complete server/unit suite PASS: 368/368 files and 1,877/1,877 tests (bunx vitest run --project server, Railway SUCCESS 35c155cf-868a-4d42-8a86-d34df7aa162a). Tested with upstream-CI-matched Node 24.19.0, Bun 1.4.4, full frozen-lockfile install and CI mode. Chromium/production-mode web sub-suites were not run.
  • Linting passes — Oxlint (0 errors/warnings), Svelte ESLint and oxfmt --check on modified frontend files.
  • Manually tested — exact proposed upstream build has not performed a controlled live Bluesky write. A separate downstream gallery implementation has published six- and eight-image posts; that is contextual evidence, not acceptance of this code.

Tests cover 1, 4, 5, 8 and 10 images; legacy/gallery embeds; quoted posts; ordered image metadata; and rejection of more than ten images or invalid media.

QA investigation: An initial isolated Railway run had 82 failing frontend test files and eight failed cURL assertions. Identical failures reproduced on unchanged upstream using that non-CI-matched runner. Reproducing OpenPost's official Node/Bun/CI environment cleared them without changing application code; the full server suite above then passed. QA-only Dockerfiles are not in this PR.

Screenshots

No layout changes; only Bluesky media-count validation/warnings change. Screenshots not applicable.

Checklist

  • My code follows the project's coding conventions (see CONTRIBUTING.md)
  • I have added tests that prove my fix is effective or my feature works
  • I have updated documentation if needed
  • I have used Conventional Commits for my commit messages
  • I have checked that there are no other PRs open for the same issue/feature (20 November 2026)

Breaking Changes

  • Yes, this PR contains breaking changes (describe what and why)
  • No, this PR does not contain breaking changes

Affected Components

  • Backend (Go)
  • Frontend (Svelte)
  • Documentation
  • Docker/Deployment
  • Database schema

Platform Impact

Does this affect any social platforms?

  • X (Twitter)
  • Mastodon
  • Bluesky
  • LinkedIn
  • Threads
  • None (general change)

Review notes

  • Generated media limits have been re-created from the Go capability catalogue (go run ./cmd/openpost-media-limits), formatted with oxfmt@0.61.0, and confirmed byte-for-byte identical to the committed guide (isolated Railway SUCCESS 3de8fe2e-75ea-489c-89c6-10c193f6c6be).
  • Preserves existing 1–4-image and video record shapes.
  • Exact gallery candidate has not yet undergone live-provider acceptance; feedback on record compatibility is welcome.
  • No migrations, deployment changes, credentials, provider tokens or production configuration are included.

@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch has not been deployed

No deployments
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.

1 participant