feat: use date-based release versions#319
Merged
Merged
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
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.
What
Add date-based public release tags and visible app versions for desktop releases.
Why
Stable releases should publish from
mainwith public versions likev2026-05-06, with.2,.3, etc. for additional UTC-day releases, while Electron/updater internals keep semver-safe versions.How
mainand publish public v-date release metadata/assets while preserving updater metadata versions.Type
feat- new featurefix- bug fixrefactor- restructure without behavior changestyle- visual/UI onlyperf- performance improvementtest- adding or updating testschore- tooling, deps, configci- CI/CD changesTest plan
Passed:
pnpm lintpnpm typechecknode --test scripts/desktop-release-metadata.test.mjspnpm --dir apps/desktop exec vitest run --config config/vitest.config.ts --project main src/main/lib/app-version-display.test.tspnpm --dir apps/desktop exec vitest run --config config/vitest.config.ts --project renderer src/renderer/src/pages/settings/general-section.i18n.test.tsxgit diff --check410 passed | 1 skipped,7399 passed | 1 skipped)Notes:
pnpm testhit a localbetter-sqlite3native module mismatch; fixed locally withbash apps/desktop/scripts/ensure-native.sh node.src/main/index.phase2.test.ts,src/renderer/src/pages/settings/settings-page.i18n.test.tsx). Both passed in isolation immediately after, and the normal pre-push hook passed on retry.Screenshots
N/A
Checklist