This update keeps the issue report template current by adding version 0.47.1 and removing outdated entries. It reduces confusion for users creating reports and improves triage accuracy for maintainers
Simplifies the Conventional Commits reference by converting it from markdown link syntax to plain text with URL, improving readability in the documentation file.
Expands Copilot instructions to enforce critical Bun-first package management workflow and prevent usage of npm/yarn/npx commands.
Adds comprehensive sections covering:
- Runtime and tooling stack details with Bun as primary runtime
- Explicit package management commands to prevent npm/yarn usage
- Performance optimization guidelines leveraging Bun's capabilities
- Testing approach using Bun's built-in test runner
- Enhanced coding standards and API integration patterns
- Cross-platform development considerations for mobile and TV
Improves developer onboarding by providing clearer context about project architecture, offline capabilities, and Chromecast support in the overview.
Extends the Discord notification system to monitor and report workflow failures in addition to pull requests.
Adds a new workflow_run trigger that listens for completed workflows on the develop branch and sends Discord notifications when any workflow fails.
Separates notification logic into two jobs: one for pull request events and another for workflow failures, each with appropriate conditional guards and using different webhook URLs for distinct notification channels.
Renames the workflow from "Discord Pull Request Notification" to "Discord Notification" to reflect the expanded scope.
Enables automated translation workflow by configuring Crowdin integration.
Sets up source translation file mapping from English to multiple language codes with update approval workflow.
Removes the skip_untranslated_files configuration to include files that may contain some untranslated strings in the export process.
This enables more comprehensive translation updates while still maintaining quality control through the skip_untranslated_strings option.
Enhances fork detection by implementing more precise repository comparison logic
and adds comprehensive debugging output to troubleshoot permission issues.
Changes null-safe comparisons to prevent false positives when repository
information is undefined, ensuring the workflow only skips comment creation
for actual cross-repository forks rather than same-repository scenarios.
Adds fork detection to skip comment operations when running from external repositories, preventing 403 permission errors.
Implements early exit when pull request or workflow run originates from a fork, and wraps comment operations in try-catch to handle remaining permission issues gracefully by logging build status instead.
Enhances the artifact comment workflow to better handle cancelled workflow runs by checking individual job statuses instead of dismissing entire workflows.
Previously, workflows marked as cancelled at the top level were completely ignored, even if some jobs within them were still running or completed successfully.
Now prioritizes active jobs over cancelled ones and validates that at least one job is actually running before processing a workflow run, preventing false negatives while still filtering out truly cancelled workflows.
Enhances artifact comment workflow to provide more accurate build status reporting by tracking individual job statuses within consolidated workflows rather than using workflow-level status.
Excludes cancelled workflow runs from consideration and prioritizes active runs over completed ones when determining build status.
Maps specific job names to build targets (Android Phone, Android TV, iOS Phone) to provide granular status information for each platform and device combination.
Improves artifact collection logic to gather artifacts when any job completes successfully, not just when entire workflow completes.
Replaces nightly.link with direct GitHub artifact URLs for better reliability.
Adds handling for cancelled builds and edge cases where workflows complete
but artifacts aren't immediately available or conclusions are pending.
Improves status messages to provide more detailed information for
unexpected build states.
Restructures the GitHub Actions workflow to better handle consolidated vs separate build workflows.
Changes the artifact collection to trigger on workflow completion rather than just success, improving visibility of failed builds.
Adds explicit fallback logic for backward compatibility with separate Android and iOS workflows.
Introduces artifact pattern matching for more reliable build target identification and adds special handling to disable iOS TV builds.
Enhances debugging output to show which workflow type is being used and lists all discovered artifacts.
Merges separate Android and iOS build workflows into a single "Build Apps" workflow to reduce duplication and simplify maintenance.
Updates the artifact comment workflow to handle both the new unified workflow and legacy separate workflows for backward compatibility during transition.
Removes redundant workflow files while preserving all existing functionality.
Replaces the repository_dispatch event system with workflow_run triggers to improve reliability and reduce complexity. The new approach automatically detects PR associations through commit SHA lookups rather than requiring manual payload construction.
Removes redundant notification steps from build workflows and simplifies the concurrency group logic. Enhances manual testing support with improved PR discovery fallbacks.
Replaces the workflow_run trigger mechanism with repository_dispatch events to enable real-time build status communication between build workflows and the artifact comment system.
Build workflows now actively notify the comment workflow when builds start, complete, or fail, providing immediate status updates rather than polling for completed workflows.
Adds real-time payload processing to display current build status and target information in PR comments, improving visibility into ongoing build processes.
BREAKING CHANGE: Changes the trigger mechanism from workflow_run to repository_dispatch, requiring build workflows to explicitly send status notifications.
Enhances the artifact comment workflow by switching from tracking all build runs to focusing on the most recent run per workflow type (Android/iOS).
Changes include:
- Increases pagination limit to capture more workflow runs
- Sorts runs by creation time to identify latest builds
- Simplifies status tracking by workflow platform rather than individual runs
- Adds detailed logging for debugging build statuses
- Improves error handling for artifact collection
- Fixes emoji rendering issue in status display
Reduces complexity while ensuring accurate status reporting for the latest builds.
Restructures the artifact comment workflow to display build progress in real-time with individual platform/device status tracking.
Changes the status table from workflow-based to target-based (Android Phone/TV, iOS Phone/TV) with dedicated status indicators and download links that update as builds complete.
Improves user experience by showing pending builds with appropriate messaging instead of waiting for all builds to finish before displaying any information.
Fixes incorrect variable reference in artifact comment generation that was using undefined `runId` instead of the proper `context.runId` from the GitHub Actions context.
Also adds descriptive job name for better workflow visibility.
Enables the workflow to run directly on pull request events (opened, synchronize, reopened) in addition to the existing workflow_run and manual dispatch triggers.
Provides immediate status updates in PR checks and improves user experience by showing workflow progress directly in the pull request interface rather than only after completion of upstream workflows.
Fixes workflow trigger condition by explicitly checking for workflow_run event type to prevent unintended executions.
Improves artifact collection reliability by switching to the correct API method and increasing page size to capture more artifacts from multiple builds.
Removes redundant artifact fetching logic that was duplicating collection efforts.
Improves the artifact comment workflow to provide better visibility into ongoing builds by:
- Triggering comments when builds start (requested event) instead of only on completion
- Using commit SHA for concurrency grouping to better handle multiple builds for the same commit
- Collecting artifacts from all recent build workflows for a PR rather than just the current run
- Adding a build status table showing progress of Android and iOS workflows
- Displaying progressive status updates even when builds are still in progress
- Enabling cancel-in-progress to prevent redundant workflow runs
This provides users with immediate feedback on build progress and comprehensive artifact availability across all platforms.
