Skip to content

chore: add engineering standards (dependabot)#2305

Open
nikzen wants to merge 1 commit into
mainfrom
chore/add-engineering-standards
Open

chore: add engineering standards (dependabot)#2305
nikzen wants to merge 1 commit into
mainfrom
chore/add-engineering-standards

Conversation

@nikzen
Copy link
Copy Markdown
Contributor

@nikzen nikzen commented Mar 24, 2026

Automated rollout from engineering-standards.

Base (always included):

  • .github/dependabot.yml – automated dependency updates (Dependabot)
  • Ecosystems: github-actions, dart
  • Grouped PRs: major updates separate from minor+patch
  • Cooldown: 14 days

Detected scope: dart

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 24, 2026

CLA assistant check
All committers have signed the CLA.

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.55%. Comparing base (ba64888) to head (fe1cc41).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2305      +/-   ##
==========================================
+ Coverage   57.16%   57.55%   +0.38%     
==========================================
  Files         159      159              
  Lines       19778    19778              
==========================================
+ Hits        11307    11384      +77     
+ Misses       8471     8394      -77     

see 10 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba64888...fe1cc41. Read the comment docs.

Comment thread .github/dependabot.yml
assignees:
- "famedly/frontend"
open-pull-requests-limit: 5
versioning-strategy: increase-if-necessary
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We must not remove the versioning-strategy for dart packages as we want to update the range for major versions only if necessary to let the consumer app in the end decide about the packages. So for packages we must use a different versioning-strategy than for apps in the dart ecosystem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants