release: set version to 0.0.1 and enable desktop packaging - #59
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prepares the desktop app for a first public release by aligning all version sources to 0.0.1 and enabling Tauri bundling/packaging so installers/artifacts are produced.
Changes:
- Bump app version to
0.0.1across frontend metadata, npm manifest, and Rust/Tauri configuration. - Enable Tauri bundling with explicit bundle targets and add installer metadata (publisher/descriptions, etc.).
- Add
license: MITtopackage.json.
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/lib/app-metadata.ts | Updates frontend APP_VERSION to 0.0.1. |
| src-tauri/tauri.conf.json | Sets Tauri version to 0.0.1 and enables bundling with targets/metadata. |
| src-tauri/Cargo.toml | Updates Rust package version to 0.0.1. |
| src-tauri/Cargo.lock | Updates the locked opencoven-chat package version to 0.0.1. |
| package.json | Updates npm version to 0.0.1 and declares license: MIT. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Sep 1, 2026
Set the application version to 0.0.1 across every surface that carries
it: the npm manifest, the Cargo package and lockfile, the Tauri config,
and the frontend app metadata. The four were previously 0.1.0, which
announced a version this project has never shipped.
Enable bundling. `bundle.active` was false, so `app:build` produced only
the raw executable and no installer of any kind. Bundling now targets
app/dmg on macOS, msi/nsis on Windows, and appimage/deb on Linux; Tauri
skips the targets that do not apply to the host.
Add the missing macOS `icon.icns`, generated from the existing 512px
`icon.png` via sips/iconutil, and reference it from the bundle icon set.
Without it a macOS build has no icon at all.
`createUpdaterArtifacts` is deliberately false: turning it on fails the
build with "plugins > updater doesn't exist" until an updater keypair and
`plugins.updater` config exist. Enabling it is release-infrastructure
work, not a version bump.
Declare the MIT license in the npm manifest to match the LICENSE file
landing alongside this release.
Verified on macOS aarch64:
pnpm typecheck pass
pnpm test:unit:normal 379 passed, 1 file skipped
pnpm lint pass (7 pre-existing demo warnings)
pnpm tauri build --bundles app,dmg OpenCoven Chat.app +
OpenCoven Chat_0.0.1_aarch64.dmg
Info.plist CFBundleShortVersionString 0.0.1
Info.plist CFBundleIconFile icon.icns
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
BunsDev
force-pushed
the
release/v0.0.1-packaging
branch
from
September 1, 2026 08:03
dd1e73b to
cc230b4
Compare
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
Closes the version and packaging blockers for the first public release.
What this changes
Version is now
0.0.1. It was0.1.0in four independent places — the npm manifest, the Cargo package, the Cargo lockfile, the Tauri config — plus the frontendAPP_VERSION. All five now agree on0.0.1.Packaging is enabled.
bundle.activewasfalse, sopnpm app:buildproduced only the raw executable and no installer of any kind. Targets are nowapp,dmg,msi,nsis,appimage,deb; Tauri skips the ones that do not apply to the host.The macOS
icon.icnsnow exists. It was missing entirely, so a macOS build had no icon. Generated from the existing 512pxicon.pngwithsips+iconutiland wired into the bundle icon set.license: MITdeclared in the npm manifest, to match theLICENSEfile landing separately.Why
createUpdaterArtifactsis falseSetting it to
truefails the build outright:There is no
plugins.updatersection and no updater keypair in this repo. Turning updater artifacts on is release-infrastructure work with its own signing key; it is not part of a version bump. v0.0.1 ships without auto-update, deliberately.Verification
Run on macOS aarch64:
pnpm typecheckpnpm test:unit:normalpnpm lintpnpm tauri build --bundles app,dmgOpenCoven Chat.app+OpenCoven Chat_0.0.1_aarch64.dmg(3.8 MB)Info.plistCFBundleShortVersionString0.0.1Info.plistCFBundleIconFileicon.icnsInfo.plistCFBundleIdentifierai.opencoven.chatNotes for reviewers
harnessAuthorityinphase1-conformance.lock.jsonis touched, so this needs no conformance repin and will not collide with the in-flight conformance PRs.chatAuthoritypinssrc-tauri/Cargo.tomlandCargo.lock, but it is verified against a clone oflock.chat.revision(the released revision), not this PR's tree — confirmed inscripts/phase1-conformance.mjs,createExactCheckouts. So the version bump does not invalidate it.OpenCoven Chat_0.0.1_aarch64.dmg. Release tooling must quote paths.