3 people 289fcb00e2 fix(ci): desktop — translate PEP 440 .devN to SemVer for Tauri (#360) ...

Tauri's build script enforces strict SemVer
(`MAJOR.MINOR.PATCH[-pre][+build]`) on `tauri.conf.json > version`, but
the autotag scheme introduced in #358 emits PEP 440 dev releases like
`1.0.2.dev661` — PEP 440 separates dev with `.`, SemVer requires `-`.
First post-#358 desktop run failed with:

    tauri.conf.json > version must be a semver string

PyPI requires PEP 440; Tauri requires SemVer. They genuinely don't
agree on `.devN`. Translate just for the Tauri bundle:

  1.0.2.dev661  -> 1.0.2-dev.661   (valid SemVer prerelease)
  1.0.2          -> 1.0.2          (passthrough)
  1.0.0-rc.1     -> 1.0.0-rc.1     (passthrough)

Tag, git history, PyPI wheel, and the updater's `latest.json` all keep
the PEP 440 form. Only the embedded bundle version uses SemVer, and
the comparison the updater does is bundle-vs-latest.json (both SemVer
now) so the upgrade path stays consistent.

Failing run for reference: 26118619500

Co-authored-by: krypticmouse <herumbshandilya123@gmail.com>

2026-05-19 12:22:24 -07:00

..

clone-stats

chore: update clone traffic data [skip ci]

2026-05-19 07:16:45 +00:00

ISSUE_TEMPLATE

feat(mining): Pearl mining integration

2026-05-05 19:11:15 -07:00

workflows

fix(ci): desktop — translate PEP 440 .devN to SemVer for Tauri (#360)

2026-05-19 12:22:24 -07:00

CODEOWNERS

release: v1.0.0 (#349)

2026-05-16 13:47:23 -07:00

pull_request_template.md

docs: add contributor docs, community infrastructure, and roadmap rewrite

2026-03-17 03:24:26 +00:00