build-feed: 0.5 support, run the feed keywords in --check, and keep partOf.offers consistent (plus: ote-migrate does not exist) #97

Activity

1. hhkaos

   added a commit that references this issue on Nov 4, 2026

   feat(build-feed): the 0.5 feed fields, and contributing's inheritance

   ...

   263214f
2. hhkaos commented on Nov 4, 2026

   

   hhkaos

   on Nov 4, 2026

   ContributorAuthor

   More actions

   0.5/0.6 support landed in 263214f. Leaving this open for ote-migrate, which is the only part left.

   Done:

   • contributing, covers and alternates are read from ote.config.json and carried into the feed. Shape only is checked here; the feed schema owns the rest once the feed is assembled.
   • contributing is inherited feed→event like license. This was a real gap rather than bookkeeping: the exporters read each event's fields directly and know nothing about feed-level inheritance, so an inheritable field missing from resolveEventInheritance never reaches them. covers and alternates deliberately do not inherit — both describe the collection, not an event in it.

   The --check ask turned out to already be satisfied, which seemed worth recording rather than closing silently. All five feed-root keywords already fire — uniqueEventIds, sharedOffersConsistent, eventsNotNewerThanFeed, eventsRespectInheritedTextLanguage and 0.5's orderedCoverage — because --check validates the assembled feed through validateFeed, and the keywords are compiled into those validators rather than registered at runtime. Verified one by one against crafted feeds instead of assumed, and pinned with eight new tests.

   So partOf.offers consistency (D032) is caught today, including the case this issue named: two parts of one conference whose shared offers disagree by value. --check catches it for free.

   Still open: ote-migrate. A new package, not a flag. Worth noting the scope moved — it is now 0.4→0.6, and 0.5→0.6 is only a specVersion change since 0.6 altered no schema. The D032 pricing warning is still the only thing that justifies a package over a sed.
3. hhkaos commented on Nov 4, 2026

   

   hhkaos

   on Nov 4, 2026

   ContributorAuthor

   More actions

   Done in #112 (packages/migrate), which was the last open part of this issue — the 0.5 support, the feed-level keywords in --check and the partOf.offers consistency all landed earlier with build-feed.

   Two notes on how ote-migrate ended up differing from the scope here:

   It covers every published version, not just 0.4→0.6. The adopter this mattered most for — corunajug.org — is on 0.3, which left the support window when 0.5.0 and 0.6.0 published the same day. Checked empirically: a 0.3 feed and a 0.1 feed both become valid 0.6 by changing specVersion alone, so the wider range cost nothing and is the only version of the tool that helps the person who actually has to run it.

   It validates against the declared version directly rather than through validateDocument. validateDocument applies the support policy, which calls an out-of-window version an error — routing through it would have refused exactly the documents that need migrating.

   The D032 warning is the part that justifies a package over a sed, as this issue argued: an unscoped offer on a part of a multi-part set now reads as admission, so a workshop that really costs 240 + 60 keeps publishing, validly, that it costs 60. ote-migrate names those events and asks; it never rewrites pricing.

   Before the first release: npm trusted publishing cannot be configured for a package that does not exist yet, so @opentechevents/migrate has to be published by hand once, then have its trusted publisher added in its npm settings. publish.yml already documents this.
4. hhkaos

   closed this as completedon Nov 4, 2026