openvibers/openvibe.publishing Commits

README: 1.4.0 (search-feed) is the current release; News, Reviews, Deals, Coupons and Trade are public (it said loopback-only, not launched); the record products pin 1.4.0 (#55)

OP OpenVibers committed 23 days ago · e12333b74a · 1 file, +9 −8

Changes

ddiff --git a/README.md b/README.md
iindex 5fa233a..a1ae41e 100644
---- a/README.md
++++ b/README.md
@@@ -3,18 +3,19 @@
> Shared publishing packages for the OpenVibe publication products: Wiki, Blog, News, Reviews,
> Deals, Coupons and Trade.
--**Status:** alpha, **1.3.0**: the stores run on PostgreSQL through the `openvibe-sdk/db` async data
++**Status:** alpha, **1.4.0**: the stores run on PostgreSQL through the `openvibe-sdk/db` async data
layer (ADR-035: PostgreSQL 18 behind PgBouncer in production, PGlite in tests). Every store method is
async, takes the product's `openvibe-sdk/db` handle, and accepts the caller's transaction handle; each
store gives its DDL as `schema(prefix)` for the product's migrations. v1.1.0 adds the shared ingest
chassis (`openvibe-publishing/ingest`) and publication glue (`openvibe-publishing/publication`) —
additive, no existing export changed. v1.2.0 adds `openvibe-publishing/layout`, the page document the
seven sites render through `openvibe-shared/shell` (additive). v1.3.0 forwards the AI summary, facts,
--`updated` and `url` through `layout.renderDocument` to the shell (additive). The exit proof (`examples/two-products`) runs in `npm test`.
--Releases v0.1.0 to v1.0.0 are tagged (see [CHANGELOG.md](CHANGELOG.md)). All seven products (Wiki and
--Blog, public at openvibe.wiki and openvibe.blog; News, Reviews, Deals, Coupons and Trade, deployed
--loopback-only, not launched) pin v1.3.0 on PostgreSQL today; each adopts a release by pinning its tag,
--and no product is released until its conversion lands.
++`updated` and `url` through `layout.renderDocument` to the shell (additive). v1.4.0 adds `openvibe-publishing/search-feed`,
++which puts a record product's pages in OpenVibe.Search (additive). The exit proof (`examples/two-products`) runs in `npm test`.
++Releases v0.1.0 to v1.4.0 are tagged (see [CHANGELOG.md](CHANGELOG.md)). All seven publication products pin v1.3.0
++on PostgreSQL today, and all seven are public: openvibe.wiki, openvibe.blog, openvibe.news, openvibe.reviews,
++openvibe.deals, openvibe.coupons and openvibe.trade. Seven record products pin v1.4.0 for the search feed: Work, Rent,
++Help, Inventory, Quest, Food and Host. Each adopts a release by pinning its tag.
**Package:** `openvibe-publishing` (CommonJS, Node ≥ 20, production runs Node 22).
**License:** MIT, like OpenVibe.Shared.
@@@ -78,8 +79,8 @@ Every module is its own entry point and can be used alone.
Pin the release tarball, like every OpenVibe package (never a `file:` link or a vendored copy):
```json
--"openvibe-publishing": "https://codeload.github.com/OpenVibers/OpenVibe.Publishing/tar.gz/refs/tags/v1.3.0",
--"openvibe-sdk": "https://codeload.github.com/OpenVibers/OpenVibe.SDK/tar.gz/refs/tags/v0.35.0",
++"openvibe-publishing": "https://codeload.github.com/OpenVibers/OpenVibe.Publishing/tar.gz/refs/tags/v1.4.0",
++"openvibe-sdk": "https://codeload.github.com/OpenVibers/OpenVibe.SDK/tar.gz/refs/tags/v0.60.0",
"pg": "^8.23.0"
```