Release 1.6.0

[github-actions[bot]]

---

name: Maintainers Only - Release about: Release checklist. title: "[MAINTAINER] [RELEASE]" labels: maintainer, release assignees: a-mabe

---

⚠️ This issue template is for maintainers only. Please do not use it unless you are a maintainer of this project. ⚠️

Release Checklist

1. Merge and Prepare for Release

• [x] Verify CI tests pass.
• [x] Merge feature branch(es) into main.
• [x] Confirm pubspec.yaml version is updated.

2. Create a Beta Pre-Release

• [x] Tag pre-release as X.Y.Z-beta.
• [x] Workflow runs to generate pre-release.
• [x] Ensure pre-release workflow has created a GitHub Issue for the release titled X.Y.Z-beta.
• [x] Ensure pre-release artifacts are built and attached to the release.
• [x] Manually upload to Google Play Open Testing & TestFlight.
  • [ ] Take new screenshots as needed.
  • [x] Create "What's Changed" text:
    • The home screen now looks and works better in both portrait and landscape.
    • Timer creation has been overhauled with a new flow and layout.
    • The “View Timer” page is gone — you’ll now edit and view timers in the same place.
• [x] Workflow manually triggered to open discussion post to advertise the beta release for open testing.

3. Beta Testing Phase

• [ ] Collect feedback and crash reports.
• [ ] If needed, create X.Y.Z-beta2.
  • [ ] Manually update the original discussion post as needed for new versions of the beta release.

Beta Testing Timeline

Patch Releases

1. [ ] Changes will be QA tested after being accepted by Google/Apple (likely 24 hours, up to 7 days).
2. [ ] After QA testing, the release will be promoted from beta testing to production.

Major and Minor Releases

1. [ ] Changes will be QA tested after being accepted by Google/Apple (likely 24 hours, up to 7 days).
2. [ ] After QA testing, the release will remain available in open testing for 7 - 10 days to recieve user feedback.
3. [ ] After the open testing period, the release will be promoted from beta testing to production.

4. Promote to Stable Release

• [ ] Run the "Promote Beta to Stable Release" GitHub Action.
• [ ] Confirm vX.Y.Z release is created with the same artifacts.
• [ ] Manually submit stable release to app stores.

5. Post-Release Tasks

• [ ] Trigger workflow to annouce the release.
• [ ] Monitor analytics and feedback.
• [ ] Start planning the next release.

[a-mabe]

Submitted for open testing through the PlayStore and AppStore. Currently awaiting approval.

Approved and discussion post created.