Different targets for development and production dependencies

[nicolasrouanne]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

It would be nice if we could configure different rules for development and production dependencies. Something such as

- uses: fastify/github-action-merge-dependabot@v3
   with:
     target:
       production: patch
       development: any

Motivation

I tend to separate devDependencies (e.g. prettier, eslint, etc.) from dependencies. Same applies in ruby for instance.
I like to merge everything that doesn't impact production as soon as it becomes available; however I'm more careful regarding packages that can impact our production app... I don't have enough coverage to be 100% sure.

Example

Here is the syntax from ahmadnassri/action-dependabot-auto-merge which is nice IMO

- match:
    dependency_name: aws-sdk
    update_type: semver:minor

- match:
    dependency_type: development
    update_type: semver:minor # includes patch updates!

- match:
    dependency_type: production
    update_type: security:minor # includes patch updates!

- match:
    dependency_type: production
    update_type: semver:patch

[MDG-MAugier]

Came to write the same thing +1

[simoneb]

The feature request is valid, but the syntax you're proposing is not valid for action inputs, in fact the action you're referring to uses an external configuration file to achieve it.

What I propose is that we introduce two more specific inputs for the action, one called target-development and the other called target-production which, if provided, override the default value provided in the target input (if any).

[github-actions]

🎉 This issue has been resolved in version 3.10.0 🎉

The release is available on:

• GitHub release

Your optic bot 📦🚀