Run test suite on flutter stable channel too

[benthillerkus]

I saw that tests on #464 were failing because of a change on flutter master channel. This turns on testing for the stable channel too, so that's easier to see if tests are failing because of a future change that cannot be adressed in code right now, or if they'd be failing in production too

Summary by CodeRabbit

• New Features
  • Introduced a "stable" release channel for our build process, allowing the system to prioritize quality checks for stable releases and improve overall targeting of enhancements.
• Chores
  • Refined workflow execution so that all tasks run to completion, even if some processes fail, resulting in more comprehensive build feedback and enhanced system reliability.

[coderabbitai]

Walkthrough

The changes update the Flutter CI workflow. A new channel, stable, is added to the matrix strategy in .github/workflows/build.yml. The conditional execution for the Check format, Analyze, and Upload coverage to codecov steps now depends on the channel being stable, replacing the former check for master. Additionally, the fail-fast property has been set to false, ensuring that all jobs run regardless of failure. The Run tests step remains unaffected by these conditions.

Changes

File	Change Summary
.github/workflows/build.yml	Added the stable channel to the matrix strategy. Modified conditionals for Check format, Analyze, and Upload coverage to codecov to run only on stable. Set fail-fast to false; Run tests step remains unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Workflow
    participant Matrix as Matrix Strategy
    participant Steps as Job Steps

    CI->>Matrix: Initialize channels (stable, master)
    Matrix-->>CI: Return selected channel
    alt Channel is "stable"
        CI->>Steps: Execute Check format, Analyze, Upload coverage
    else Other channel
        Note right of CI: Skip specific steps
    end
    CI->>Steps: Execute Run tests (always)

Loading

Poem

Oh dear, I'm a hopping bunny on a coding spree,
Updating CI with a twist as clever as can be.
The "stable" channel now leads the way,
With tests all marching out, come what may.
A joyful hop, a twirl, a digital cheer—
Flutter flows smoothly, and the rapids clear!
🐰🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca0b17f and 7b273ee.

📒 Files selected for processing (1)

• .github/workflows/build.yml (3 hunks)

🔇 Additional comments (5)

.github/workflows/build.yml (5)

19-20: Add "stable" channel to CI matrix.

The addition of the "stable" channel here broadens the test environment to include the production-like Flutter stable channel, aligning with the PR’s objective.

---

21-21: Set "fail-fast" to false.

Setting fail-fast to false ensures that all jobs run regardless of individual failures. This is especially useful when testing on multiple channels, as it allows comprehensive output for analysis.

---

33-36: Run "Check format" only on the stable channel.

By restricting the "Check format" step with if: matrix.channel == 'stable', the workflow now executes code style checks on the stable channel only. This isolates production-level checks from potential early-stage issues on non-stable channels. Please verify that this is the intended behavior.

---

38-41: Apply conditional execution for "Analyze" step.

Limiting the "Analyze" step to run only on the stable channel ensures that static analysis is performed in an environment similar to production. This helps in distinguishing issues unique to development channels.

---

47-50: Restrict "Upload coverage to codecov" to the stable channel.

The added condition ensures that code coverage data is uploaded only when running on the stable channel, which can prevent noise from potentially less-stable builds. This supports clearer differentiation between planned changes and channel-exposure issues.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[rrousselGit]

Thanks!