ci: run unit tests on main once a day

[zimeg]

Summary

This PR runs the unit tests once a day to confirm the latest versions of scoped requirements continue to pass 🤖

Related: slackapi/python-slack-sdk#1697
Perhaps also #1317: https://github.com/slackapi/bolt-python/actions/runs/15833832234/job/44799314169

Testing

If this is merged to main I believe the tests will repeat! Reference: schedule

I'm hoping to run the tests in CI with this PR also 👾 ✨

Notes

I'd be open to making a similar change for other testing related workflows, but this might be enough to catch problems soon?

• codecov.yml
• flake8.yml
• mypy.yml

Category

• Others

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've run ./scripts/install_all_and_run_tests.sh after making the changes.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.96%. Comparing base (7f9ae9c) to head (2be932e).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1319   +/-   ##
=======================================
  Coverage   90.96%   90.96%           
=======================================
  Files         222      222           
  Lines        7501     7501           
=======================================
  Hits         6823     6823           
  Misses        678      678           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zimeg]

🔍 https://github.com/slackapi/bolt-python/actions/runs/15888693157/job/44806750500?pr=1319#step:11:50

An update to asyncio might be causing CI now to error, but I'm not sure what's causing this?

tests/adapter_tests_async/test_async_asgi.py:60
  /home/runner/work/bolt-python/bolt-python/tests/adapter_tests_async/test_async_asgi.py:60: PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
    @pytest.mark.asyncio

The plugins from these tests are interesting to me since I'm installing different versions, but am also not sure how to match this:

- plugins: anyio-3.7.1, cov-4.1.0
+ plugins: anyio-4.9.0, cov-6.2.1, asyncio-0.26.0

[zimeg]

📝 And a note of these changes for the kind reviewers!

[zimeg]

⌛ This was also a quick value that I'm so open to changing per suggestion 🙏 ✨

https://crontab.guru/#0_0___*

[WilliamBergamin]

Thanks for putting this together 💯

One question before I approve this; if these tests fail where will they report their failure?

[zimeg]

@WilliamBergamin And thank you for the updates to tests 🫡

if these tests fail where will they report their failure?

I've found that "watching" all activity on a project sends failing CI from main to the notifications tab but also this might appear on the last commit to main 🔍

The notifications are something similar to this IIRC:

[WilliamBergamin]

Looks good 💯

Should we consider using our Github action to send errors to our triage channel?