Skip to content

Conversation

@altaskur
Copy link
Owner

@altaskur altaskur commented Feb 6, 2026

Description

Goal

Key Changes

Type of Change

  • πŸ› Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ’₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ“ Documentation update
  • 🎨 Style/UI changes
  • ♻️ Refactoring (no functional changes)
  • ⚑ Performance improvement
  • βœ… Test updates
  • πŸ”§ Build/configuration changes

Impact Assessment

Database Impact

  • No database changes
  • New migration(s) included
  • Existing data migration required

Backup Impact

  • No impact on backups
  • Backup format changed
  • Restore compatibility maintained

Testing

How Has This Been Tested?

Description

Bump version to 1.0.0-alpha.4, update package dependencies, and integrate the automatic update system using electron-updater.

Goal

Prepare the alpha.4 release with an automatic update mechanism so users can receive new versions without manually downloading them. Also updates dependencies to their latest compatible versions.

Key Changes

  • Bump version from 1.0.0-alpha.3 to 1.0.0-alpha.4
  • Add automatic update system via electron-updater (UpdateManager, IPC handlers, Angular UpdateService, UI dialog and settings page)
  • Add i18n translations (en/es) for the update system
  • Update and consolidate package dependencies (package-lock.json refresh)
  • Improve documentation (README, CONTRIBUTING, SonarQube guide)
  • Fix large project name styles (community contribution)

Type of Change

  • πŸ› Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ’₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ“ Documentation update
  • 🎨 Style/UI changes
  • ♻️ Refactoring (no functional changes)
  • ⚑ Performance improvement
  • βœ… Test updates
  • πŸ”§ Build/configuration changes

Impact Assessment

Database Impact

  • No database changes

Backup Impact

  • No impact on backups

Testing

How Has This Been Tested?

  • Unit tests
  • Integration tests
  • Manual testing
  • Tested with SonarQube analysis

Test Steps

  1. Run npm run prisma:generate then npm run dev β€” verify the app launches without errors
  2. Navigate to Settings β†’ Updates β€” verify the update settings page renders correctly
  3. Run npm run sonar:check β€” verify all tests pass and quality gate is met

Test Configuration

  • Node version: v24.13.0
  • npm version: 11.9.0
  • Platform tested: Windows

UI Changes

Before

No update UI existed β€” users had no way to check for or manage application updates from within the app.

After

  • New Update dialog component (open-update-dialog) shows update availability, download progress, and release notes
  • New Settings β†’ Updates page (open-settings-updates) allows users to configure automatic update checks and view update history

Checklist

- Added "hono" version 4.11.8 and "lodash" version 4.17.21 to overrides.
- Moved "@electron/rebuild" to the devDependencies section.
- Updated "prisma" from version 6.19.2 to 7.1.0.
chore: bump version to 1.0.0-alpha.4 in package.json
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 6, 2026

@altaskur altaskur merged commit 96e6c99 into main Feb 6, 2026
6 checks passed
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Prepares the 1.0.0-alpha.4 release by wiring update-related functionality across the Electron and Angular layers, and adding/adjusting unit tests to cover the new update/version surfaces.

Changes:

  • Bump app version and adjust build tooling dependencies (switch to @electron/rebuild).
  • Add/update unit tests for retrieving the app version via the update API.
  • Add a new Angular spec suite for the Settings β†’ Updates page behavior.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File Description
src/app/services/update/update.service.spec.ts Adds unit tests for UpdateService.getAppVersion() success and failure paths.
src/app/pages/open-settings-updates/open-settings-updates.spec.ts Introduces component tests for the Updates settings page interactions and UI behaviors.
electron/src/services/ipc/update-handlers.spec.ts Extends IPC handler tests to cover the new update:get-app-version handler.
package.json Bumps version and updates overrides/devDependencies and postinstall rebuild behavior.

πŸ’‘ Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"prisma:migrate": "cross-env DATABASE_URL=file:./dist/data/timetracker.db prisma migrate dev",
"prisma:template": "node scripts/update-db-template.mjs",
"postinstall": "electron-rebuild",
"postinstall": "npx @electron/rebuild",
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

postinstall runs npx @electron/rebuild, but @electron/rebuild exposes the CLI bin as electron-rebuild (see package-lock bin: { "electron-rebuild": ... }). To avoid install failures under npm exec/npx resolution rules, invoke the actual bin (e.g., npx electron-rebuild or electron-rebuild) instead of the package name.

Suggested change
"postinstall": "npx @electron/rebuild",
"postinstall": "electron-rebuild",

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant