Chronly 0.1.0 RC11

A release candidate for testing, built from 4d89809. The automated unit, Chromium, and Firefox suites passed; the manual checks in RELEASING.md have not been signed off.

What's Changed

• Redesign the popup, make every alert actionable, and test it end to end in Chrome and Firefox by @fredrikblau in #7
• Add Undo, snooze length, gentle wake, and a notifications warning by @fredrikblau in #16
• Release from the Actions tab or a release made on GitHub; harden the workflow; fix a flaky Undo locator by @fredrikblau in #17

New Contributors

• @fredrikblau made their first contribution in #7

Full Changelog: v0.1.0-rc.10...v0.1.0-rc.11

Chronly 0.1.0 RC9

Chronly 0.1.0 RC9 protects saved state when extension storage or worker tasks fail.

What changed

• The popup disables controls while saved data loads. If a read fails, Chronly removes fallback controls and asks the user to reopen the popup.
• Stopwatch persistence recovers after a rejected write and reports the failure.
• The offscreen player releases failed playback IDs so later alarm delivery can retry.
• Background event logs now name the failed task and its record, alarm, or notification context.

Verification

CI passed 286 unit and component tests plus five Chromium extension flows. Regressions cover pending and rejected popup hydration, stopwatch queue recovery, offscreen playback retry, and background task diagnostics.

The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks tracked in issue #5. Treat this as a test build.

Install and test

Download the Chrome or Firefox ZIP below. Follow the repository installation instructions, then report results in issue #5.

Artifact checksums

• Chrome: f1245ef606925a4be7f9239a2399dbf799dfc006c5d57b91883f7f362e44b720
• Firefox: 67d5d6911babf733a1c8f0346498118cce7e8d41fe64700f5116358cf8eb6bab
• Sources: 6817198086fe35d996ec452a432863f470e3009c85191b191360e20275b0c979

Chronly 0.1.0 RC8

Chronly 0.1.0 RC8 keeps alarm, timer, and Pomodoro controls recoverable when browser storage rejects a write. It also prevents timer restart from deleting the existing timer after a failed replacement.

What changed

• Creation forms wait for storage before clearing draft labels or repeat days. They block duplicate writes and show a retry message after failure.
• Pause, resume, restart, stop, and delete actions report storage failures.
• Timer restart updates the existing record in one write.
• Notification acknowledgement stops sound and clears the alert even if record cleanup fails.

Verification

CI passed 281 unit and component tests plus five Chromium extension flows. Regressions cover all three creation forms, single-write timer restart, and dismissal cleanup after rejected storage.

The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks tracked in issue #5. Treat this as a test build.

Install and test

Download the Chrome or Firefox ZIP below. Follow the repository installation instructions, then report results in issue #5.

Artifact checksums

• Chrome: 6ae15e6b04747650a280e357fdb21b25256d9a3e5f14decd463ed41c4c08c562
• Firefox: 485ab3fc4c02d18520f555b6c338166b1f7b1d2e7d981bcb0317286eaae5566e
• Sources: 49bfd5690c2e54da87b56a4fe60802d9179cb506e27017f925758d3c056d2473

Chronly 0.1.0 RC7

Chronly 0.1.0 RC7 prevents concurrent alarm, timer, and Pomodoro changes from overwriting one another when the popup and background process write at the same time. It includes the prior persistence and alert-audio fixes.

What changed

• Record changes now use one browser-native lock across popup and background contexts.
• A delivery update can no longer restore a record deleted while an alert is firing.
• Concurrent timer restarts, edits, and deletions preserve each intended change.

Verification

CI passed 276 unit and component tests plus five Chromium extension flows. The new regressions deliberately overlap writes from separate store instances. The built-extension flow confirms the locking API exists in both the popup and MV3 service worker. All three release packages passed manifest and Firefox lint checks.

The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Chronly 0.1.0 RC6

Chronly 0.1.0 RC6 makes imported-sound removal safe when browser local storage is slow or unavailable. It includes the prior persistence and alert-audio fixes.

What changed

• Custom-sound imports and removals now run in order, so concurrent changes preserve each saved file and the queue recovers after a failed write.
• The Remove action waits for storage. Chronly leaves the sound selected and restores Remove for retry when storage rejects the write. The panel reports the error.

Verification

CI passed 274 unit and component tests plus five Chromium extension flows. All three release packages passed manifest and Firefox lint checks. CI reloads the popup after import and removal to verify both storage operations.

The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC6 field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Chronly 0.1.0 RC5

Chronly 0.1.0 RC5 prevents rapid appearance changes from overwriting one another and reduces browser sync writes. It includes the world-clock and alert-audio reliability fixes from earlier candidates.

What changed

• Appearance updates now run in order and merge background changes against the latest saved settings. The queue remains available after a rejected write.
• Text-size, contrast, and persisted colour controls save once per committed change. Both appearance panels show a retryable error when browser storage rejects a write.

Verification

CI passed 272 unit and component tests, five Chromium extension flows, all three release packages, manifest checks, and Firefox package lint. The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC5 field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Chronly 0.1.0 RC4

Chronly 0.1.0 RC4 keeps world-clock changes safe when browser sync storage rejects a write. It includes the alarm-audio and imported-sound reliability fixes from RC3.

What changed

• World-clock add, reorder, and remove actions wait for extension storage before accepting another change.
• A failed add keeps the entered zone and label, shows a retryable error, and re-enables the form.
• Public capacity claims now match the finite storage quotas enforced by Chrome and Firefox.

Verification

CI passed 268 unit and component tests, five Chromium extension flows, all three release packages, manifest checks, and Firefox package lint. The maintainer has not completed the packed Chrome alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC4 field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Chronly 0.1.0 RC3

Chronly 0.1.0 RC3 fixes two audio reliability races and opens GitHub Discussions for questions and design ideas.

What changed

• Repeated delivery of the same alert no longer starts overlapping sound loops.
• Imported audio appears in the picker after extension storage saves it, so closing or reloading the popup cannot outrun the write.
• The issue chooser and contributor guide now route questions to GitHub Discussions.

Verification

CI passed 267 unit and component tests, four Chromium extension flows, both browser builds, manifest checks, and Firefox package lint. The maintainer has not completed the packaged alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build, not a stable or store release.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC3 field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Priority test areas:

• Alarm or timer sound continues until you dismiss the notification.
• One overdue alert fires after the computer sleeps past its due time.
• Timers, stopwatch state, world clocks, and settings survive Chrome restarts.
• Firefox plays alarm audio from a temporary install; advanced testers can cover restart persistence through the field-test issue's development-browser path.

Chronly 0.1.0 RC2

Chronly 0.1.0 RC2 fixes cleanup when an alarm, timer, or Pomodoro is deleted.

What changed

• Deleting a scheduled record now clears its native browser alarm.
• Deleting a ringing record now clears its notification and stops its sound.
• The real Chromium extension test now verifies native alarm creation, service-worker restart recovery, and deletion cleanup.

Verification

CI passed 264 unit and component tests, four Chromium extension flows, both browser builds, manifest checks, and Firefox package lint. The maintainer has not completed the packaged alarm, sleep and wake, or Firefox restart and audio checks in the stable release checklist. Treat this as a test build, not a stable or store release.

Test it

Chrome

1. Download and unzip the Chrome test build.
2. Open chrome://extensions, enable Developer mode, and choose Load unpacked.
3. Select the unzipped folder.

Firefox

1. Download the Firefox temporary test build.
2. Open about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
3. Select the downloaded ZIP.

Firefox unloads temporary add-ons at restart. Use this path for popup, alarm audio, notification, and native New Tab checks. Restart testing requires an AMO-signed candidate or a dedicated Firefox Developer Edition or Nightly profile configured for unsigned add-ons.

The Firefox reviewer source archive contains the pinned source and build instructions. Users do not need it.

Send feedback

Post structured results in the RC2 field-test issue, or open a separate issue for a defect. Include your browser version, operating system, steps, expected result, and actual result.

Priority test areas:

• Alarm or timer sound continues until you dismiss the notification.
• One overdue alert fires after the computer sleeps past its due time.
• Timers, stopwatch state, world clocks, and settings survive Chrome restarts.
• Firefox plays alarm audio from a temporary install; advanced testers can cover restart persistence through the field-test issue's development-browser path.

Chronly 0.1.0 RC10

With Chronly 0.1.0 RC10, you can spot notification and audio failures before you trust an alarm.

What changed

• You see an accessible error when the alarm Test fails to create a notification or play audio.
• You see an accessible error when the selected sound preview fails.

Verification

We ran 288 unit and component tests plus five Chromium extension flows. In the two new regressions, we reject notification creation and sound playback.

The maintainer needs to complete the five tracks in issue #5, including packed Chrome timing and Firefox restart/audio. Treat this as a test build.

Install and test

Download the Chrome or Firefox ZIP below. Follow the repository installation instructions, then report results in issue #5.

Artifact checksums

• Chrome: 2f3d54cbe16c6a78489c46250d1256fddbe720e5f79e378d106a1a0364e7d16b
• Firefox: dbf54f0368657c4ffd0fe5ff627aa48b8c3bbf5d38d29faa078aaefec2466867
• Sources: ffcebb967e543acff717c99ea00a260d0219086558ff560f5da642bc9f89d104