Skip to content

dependabot: replace wildcard release/* target-branch with explicit per-branch entries#26936

Open
Copilot wants to merge 3 commits intomasterfrom
copilot/update-dependabot-target-branches
Open

dependabot: replace wildcard release/* target-branch with explicit per-branch entries#26936
Copilot wants to merge 3 commits intomasterfrom
copilot/update-dependabot-target-branches

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 3, 2026

Dependabot does not support wildcard patterns in target-branch, making the existing release/* entries non-functional. Replaces them with explicit entries for each active release branch.

Changes

  • github-actions ecosystem: Replaced single target-branch: "release/*" entry with three entries targeting release/v7.4, release/v7.5, and release/v7.6
  • docker ecosystem: Same expansion to explicit per-branch entries
  • Formatting normalization: Quoted directory: "/" and interval: "daily" consistently across all entries (previously unquoted in the docker master-targeting entry)

Result

8 total updates entries (was 4): master + 3 release branches for each of github-actions and docker.

  - package-ecosystem: "github-actions"
    directory: "/"
    target-branch: "release/v7.4"
    schedule:
      interval: "daily"
    labels:
      - "CL-BuildPackaging"

  - package-ecosystem: "github-actions"
    directory: "/"
    target-branch: "release/v7.5"
    ...
Original prompt

Create a pull request in PowerShell/PowerShell to update .github/dependabot.yml so Dependabot updates target each release branch explicitly instead of using the unsupported wildcard release/*.

Context:

Required changes:

  1. Replace the github-actions entry that currently has target-branch: "release/*" with three separate updates entries, each identical except target-branch set to one of:

    • release/v7.4
    • release/v7.5
    • release/v7.6
      Keep labels and schedule interval daily.
  2. Replace the docker entry that currently has target-branch: "release/*" with three separate entries, each targeting one of the same release branches.

  3. Normalize YAML formatting for consistency:

    • Use directory: "/" everywhere.
    • Use schedule.interval: "daily" (quoted) everywhere.
  4. Ensure the resulting YAML remains valid and keeps the existing master-targeting entries.

Open the PR against the master branch.

This pull request was created from Copilot chat.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…wildcard

Co-authored-by: TravisEz13 <10873629+TravisEz13@users.noreply.github.com>
Copilot AI changed the title [WIP] Update Dependabot configuration for explicit release branches dependabot: replace wildcard release/* target-branch with explicit per-branch entries Mar 3, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Mar 7, 2026
@TravisEz13 TravisEz13 added the CL-Tools Indicates that a PR should be marked as a tools change in the Change Log label Mar 18, 2026
@TravisEz13 TravisEz13 marked this pull request as ready for review March 18, 2026 18:52
@TravisEz13 TravisEz13 requested review from a team and jshigetomi as code owners March 18, 2026 18:52
Copilot AI review requested due to automatic review settings March 18, 2026 18:52
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates Dependabot configuration to avoid unsupported wildcard target-branch: "release/*" entries by explicitly targeting each active release branch, ensuring Dependabot PRs are created against the intended release branches.

Changes:

  • Expanded github-actions updates from a single release/* target to explicit entries for release/v7.4, release/v7.5, and release/v7.6.
  • Expanded docker updates similarly to explicit per-release-branch entries.
  • Normalized YAML formatting for directory and schedule.interval quoting for consistency.

@microsoft-github-policy-service microsoft-github-policy-service Bot removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Mar 18, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot added the Review - Needed The PR is being reviewed label Mar 26, 2026
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

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

Labels

CL-Tools Indicates that a PR should be marked as a tools change in the Change Log Review - Needed The PR is being reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants