Обновления

Backend release publication reliability — 0.0.3.81

Fixes release-news asset staging so signed Backend release descriptors can be checksummed and published without weakening immutable release validation.

Только чтение Аватар SlavikSlavikov SlavikSlavikov @SlavikSlavikov 11 окт. 2026 г. 0 ответов

Основное сообщение темы

Backend release publication reliability

Fixes release-news asset staging so signed Backend release descriptors can be checksummed and published without weakening immutable release validation.

Release reliability

Reliable release-news asset publication

Stages the validated authored release-news sidecar under the canonical release asset name and verifies both published and comparison copies against its authenticated digest before checksumming.

Backend improvements

Improved mod-catalog settings and metadata

Restores mod-catalog settings, provider, TOML, image, and catalog metadata.

More reliable profile media and runtime recovery

Refreshes expired Launcher profile media caches on demand, waits for public Backend readiness in development, and recovers authenticated profile-envelope renewals after interrupted pointer commits before startup validation. Invalid typed signatures are rejected before any recovery write.

Safer Java runtime catalog handling

Preserves private Java runtime catalog inputs, matches complete Zulu/OpenJDK build identities, and atomically promotes private directory selectors.

Resumable Backend runs

Resumes a successfully stopped, same-owner Backend run with retained data and a newly issued Website lease after owner-state regeneration.

Additive database compatibility

Carries forward the v0.0.3.79 migration plan from the v0.0.3.77 baseline through the support-version sort key. No existing data is dropped.

Обсуждение только для чтения

Вы можете читать эту тему, но публикация сейчас недоступна для вашего аккаунта или этой категории.

Обсуждение

Ответы

Ответов пока нет

Пока нет ответов. Начните обсуждение первыми.