Repository navigation
chore(release): prepare v0.0.49 - #175
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare v0.0.49 from the verified main branch, including the pre-release display fixes in #174. This PR changes release metadata only; plugins and worlds keep their independent versions.
The release covers recovery and streaming reliability, background-job status, storage and plugin boundary fixes, desktop layout fixes, and the switch to Node's built-in SQLite driver.
Evidence
After: fix: resolve pre-release timeline and form display defects #174 joins reasoning to the durable source job without hiding real failures and omits only a duplicate template full stop. Regression tests went from failing to passing; the isolated native session restored four successful extract jobs without orphan errors, and the actual generated form was replayed successfully.
After: All 19 versions identify v0.0.49; upgrade notes distinguish this release from v0.0.48's older breaking-data boundary.
Verification
pnpm check;pnpm test(43 successful tasks, including 249 Web test files / 1,792 tests);pnpm test:pg(1,165 store + 28 server tests);pnpm e2e(132 passed, 6 optional cases skipped);pnpm release:preflight;pnpm --filter @covel/desktop build; andpnpm --filter @covel/desktop smoke:restart.codex/gpt-6-lunaroute.88870f9e2ca9611b40eaf1fed04bca2d1857c5c7. Both macOS arm64 and Windows x64 packaging, resource/startup verification, and Windows package-installation API checks passed. Publishing was disabled for the dry run.v0.0.49on merge commit5151f152f6ca4cd362b6e81aeab405227335b36a, after main CI and Docs passed. The release workflow succeeded; its macOS job was rescheduled after a runner queue stall, retaining the successful checks and Windows artifact.Not verified: Interactive Windows gameplay, other model providers, real image/audio generation, and long playthroughs of every world. Windows native CI builds and API tests do not establish a full Windows player acceptance run. The six optional live-model Playwright cases are skipped by the deterministic suite.
Upgrade notes
Existing v0.0.48 SQLite databases remain readable; no database deletion or migration is required for the driver replacement. Older-version restrictions remain documented separately. Custom storage backends must implement
releaseStaleSuspensionClaims, and plugins must support the host version in any declaredcovelrange. macOS and Windows artifacts remain unsigned; macOS is not notarized.Docs sync and context
docs/CHANGELOG.mdare synchronized. The previous Unreleased entries become the dated release section.ONBOARDING_VERSIONremains 4 because this release adds no tutorial step.Merge Danger
Door: Two-way before tagging; published tags and artifacts will not be rewritten.
Blast Radius: Release
Merge only after candidate CI and both desktop packaging jobs pass. Then create an annotated v0.0.49 tag on the exact main merge commit and let the tag workflow publish the release.