Skip to content

ci: automerge updates to dependencies after running tests#239

Merged
zimeg merged 1 commit into
mainfrom
zimeg-ci-automerge-deps
Oct 8, 2025
Merged

ci: automerge updates to dependencies after running tests#239
zimeg merged 1 commit into
mainfrom
zimeg-ci-automerge-deps

Conversation

@zimeg
Copy link
Copy Markdown
Member

@zimeg zimeg commented Oct 8, 2025

Summary

This PR automerges updates to dependencies matching patch or minor versions from the most kind @dependabot!

Reviewers

I'm so curious if this is the right scope of dependencies to merge? When merging these I often use CI passing as validation while keeping watch for CVEs appearing later.

This automation matches that in a workflow. Before releasing a version to the public we might confirm dependencies continue to match our expectations 🤖 🔐 ✨

Notes

Some changes are required to configurations of repositories:

  • Allow auto-merge: This must be allowed!
  • Branch protection: "Require status checks to pass before merging" ought be true and include all relevant tests!
  • Branch protection: "Require branches to be up to date before merging" might be true also.

Related reading: https://github.blog/changelog/2025-10-06-upcoming-changes-to-github-dependabot-pull-request-comment-commands/

Requirements

@zimeg zimeg added this to the Next Release milestone Oct 8, 2025
@zimeg zimeg self-assigned this Oct 8, 2025
@zimeg zimeg requested a review from a team as a code owner October 8, 2025 21:59
@zimeg zimeg added code health M-T: Test improvements and anything that improves code health semver:patch Use on pull requests to describe the release version increment build M-T: Changes to compilation and CI processes labels Oct 8, 2025
@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.00%. Comparing base (9ae0867) to head (e95993d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
- Coverage   63.01%   63.00%   -0.01%     
==========================================
  Files         212      212              
  Lines       21857    21857              
==========================================
- Hits        13773    13772       -1     
- Misses       7016     7020       +4     
+ Partials     1068     1065       -3     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Member

@mwbrooks mwbrooks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Super cool, thanks for bringing this into the Slack CLI repo!

🧠 I agree that semver:patch and semver:minor are safe scopes to have auto-approval and auto-merge. For minors, it's nice to look over the CHANGELOG to know what's new, but this shouldn't block merges.

🤖 I'm down to give this a try!

@zimeg
Copy link
Copy Markdown
Member Author

zimeg commented Oct 8, 2025

@mwbrooks I'm excited as well!

Hoping this lets us continue to develop with the latest changes so I'll merge this. Will report back having updated the settings of this repository with #236 #237 #238 soon 🤖 ✨

@zimeg zimeg merged commit 577c052 into main Oct 8, 2025
6 checks passed
@zimeg zimeg deleted the zimeg-ci-automerge-deps branch October 8, 2025 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build M-T: Changes to compilation and CI processes code health M-T: Test improvements and anything that improves code health semver:patch Use on pull requests to describe the release version increment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants