Releases · unfoldingWord/dcs

01 Oct 10:11

richmahn

v1.20.4-dcs

Release of Gitea v1.20.4 with DCS customizations. Upgrades to Gitea v1.20.4. See the CHANGELOG for Gitea changes.

Fixes:

Features:

Adds the /api/v1/languages/langnames.json and /api/v1/languages/langnames_keyed.json endpoints. See the "languages" in the swagger for more details: https://git.door43.org/api/swagger
Allows catalog API search endpoint to search for all branches with stage=branch&includeHistory=1
Uses Github actions to build docker image for release

Assets 2

29 Aug 17:51

richmahn

v1.20.3-dcs

Release of Gitea v1.20.3 with DCS customizations. Upgrades to Gitea v1.20.3. See the CHANGELOG for Gitea changes.

Bug fix:

Fixed books listed in a Scripture Burrito's metadata.
UI Explore / Catalog / Org pages were NOT searching by subject (was being ignored).
Catalog release badges now appear on repo listing pages
Fixes assets in Release property of Catalog Entries so they show in catalog search API results
Fixes includeHistory to properly show all releases in catalog search API results
Fixes languages, subjects and owners catalog API endpoints so they show data
Fixes catalog property of repo API response object to be properly populated

Assets 80

20 Aug 01:46

richmahn

v1.20.2-dcs

Release of Gitea v1.20.2 with DCS Customizations:

See the CHANGELOG for [breaking] changes, fixes and new features of v1.18.X, v1.19.X, v1.20.0, v1.20.1 and v1.20.2

DCS Features:

This introduces MULTIPLE metadata types to the DCS Catalog (formally Catalog Next): SB (Scripture Burrito), RC (Resource Container, which was previously the only one validated and catalogued), TS (translationStudio) and TC (translationCore). Metadata Type and Metadata Version can be used to query the catalog and used on the Explore page. See the help given in the search button info icon at https://git.door43.org/explore/repos or in the API swagger.
For a Release to be catalogued, the tag must either start with v# (v and a number) or a year (4 digits) to be accepted as a release, as other releases for some repos were not actual releases, but tests and stages.
Scripture Burrito metadata.json files are also validated by the Scripture Burrito schema found here.
A new "Metadata" page has been added to the repo page (top tabs) so you can view what metadata each branch or release has. For example: https://git.door43.org/unfoldingWord/en_tn/metadata
A new status bar icon has been added for the metadata type and version as well, next to the repo's language status on the repo home page. It is clickable to search for other repos of the same metadata type.