Skip to content

Post, Release and ChangelogEntry storage #4

Closed

Description

@mattdjenkinson

Part of datum-cloud/enhancements#943. Updated for the CRD design: these are CRDs in Milo, and the feedback operator does what the Postgres storage did.

Not in this issue any more:

  • Re-embedding posts: dropped. There's no pgvector; similar posts come from milo-os/search (Search integration #12).
  • Release.status.posts and ChangelogEntry.status.posts: feedback-sync keeps these, in its own epic.
  • Delivery tracking: the operator writes status.delivery, but working out the stage belongs to the delivery-tracking work in a later epic.

Activity

  1. mattdjenkinson commented on Nov 18, 2026

    @mattdjenkinson
    ContributorAuthor

    Everything in scope here is merged (#32, #33, #34). I've updated the description: re-embedding is dropped, and Release.status.posts and delivery tracking move to the feedback-sync and delivery-tracking epics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions