Skip to content

Bump picomatch and update Scriban to fix CI failures#13707

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/dotnet/samples/Demos/ProcessFrameworkWithSignalR/src/ProcessFramework.Aspire.SignalR.ReactFrontend/multi-bf05dc1ecf
Closed

Bump picomatch and update Scriban to fix CI failures#13707
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/dotnet/samples/Demos/ProcessFrameworkWithSignalR/src/ProcessFramework.Aspire.SignalR.ReactFrontend/multi-bf05dc1ecf

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Mar 26, 2026

Copy link
Copy Markdown
Contributor

Motivation and Context

This PR started as a Dependabot update for picomatch in the React frontend sample.
While addressing review feedback, CI failures were investigated and traced to NuGet audit failures (NU1904/NU1903) caused by a vulnerable Scriban version in the .NET dependency graph.

Description

  • Kept the original picomatch updates in:
    • /dotnet/samples/Demos/ProcessFrameworkWithSignalR/src/ProcessFramework.Aspire.SignalR.ReactFrontend
  • Added a minimal CI fix by updating central .NET package management:
    • Scriban from 6.6.0 to 7.2.4 in dotnet/Directory.Packages.props

This aligns the PR with the actual merged scope and resolves the CI/CD failure path triggered during .NET build/test workflows.

Contribution Checklist

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps  and [picomatch](https://github.com/micromatch/picomatch). These dependencies needed to be updated together.

Updates `picomatch` from 4.0.3 to 4.0.4
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@4.0.3...4.0.4)

Updates `picomatch` from 2.3.1 to 2.3.2
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@4.0.3...4.0.4)

---
updated-dependencies:
- dependency-name: picomatch
  dependency-version: 4.0.4
  dependency-type: indirect
- dependency-name: picomatch
  dependency-version: 2.3.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file. Used by Dependabot. javascript Pull requests that update javascript code labels Mar 26, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner March 26, 2026 05:49
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file. Used by Dependabot. javascript Pull requests that update javascript code labels Mar 26, 2026

@github-actions github-actions Bot left a comment

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.

Automated Code Review

Reviewers: 4 | Confidence: 95% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach


Automated review by dependabot[bot]'s agents

@moonbox3

Copy link
Copy Markdown
Collaborator

@copilot: fix the CI/CD failures

Copilot AI review requested due to automatic review settings June 17, 2026 06:23
@dependabot
dependabot Bot removed the request for review from Copilot June 17, 2026 06:23

Copilot AI commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

@copilot: fix the CI/CD failures

Implemented in commit 38c64ef. I investigated the failing CI run logs, reproduced the NU1904/NU1903 audit failure locally, and fixed it by bumping Scriban in /dotnet/Directory.Packages.props from 6.6.0 to 7.2.4. I then re-ran targeted validation (dotnet build ... -warnaserror, dotnet test, and dotnet list package --vulnerable) and the failing path now passes.

Copilot AI changed the title Bump picomatch in /dotnet/samples/Demos/ProcessFrameworkWithSignalR/src/ProcessFramework.Aspire.SignalR.ReactFrontend Bump picomatch and update Scriban to fix CI failures Jun 17, 2026
Copilot AI requested a review from moonbox3 June 17, 2026 06:25
pull Bot pushed a commit to AmirulAndalib/semantic-kernel that referenced this pull request Jul 23, 2026
### Motivation and Context

Semantic Kernel currently has 43 open Dependabot pull requests spanning
GitHub Actions, .NET, Python, npm, and Yarn dependency graphs. This
rollup applies their compatible net changes together on the latest
`main`, making it possible to validate and merge the updates as one
coherent dependency state.

Supersedes:

- microsoft#13133
- microsoft#13134
- microsoft#13136
- microsoft#13172
- microsoft#13507
- microsoft#13601
- microsoft#13606
- microsoft#13666
- microsoft#13673
- microsoft#13688
- microsoft#13700
- microsoft#13707
- microsoft#13708
- microsoft#13712
- microsoft#13721
- microsoft#13873
- microsoft#13930
- microsoft#13939
- microsoft#13949
- microsoft#13950
- microsoft#13951
- microsoft#13997
- microsoft#14000
- microsoft#14053
- microsoft#14069
- microsoft#14088
- microsoft#14091
- microsoft#14094
- microsoft#14103
- microsoft#14106
- microsoft#14107
- microsoft#14108
- microsoft#14109
- microsoft#14110
- microsoft#14128
- microsoft#14148
- microsoft#14149
- microsoft#14160
- microsoft#14161
- microsoft#14164
- microsoft#14171
- microsoft#14172
- microsoft#14173

### Description

- Updates the requested GitHub Actions and preserves the PR-file-scoped
typos workflow fix.
- Consolidates the .NET Aspire, AWS SDK, ReportGenerator, JavaScript,
and SQLite security updates.
- Regenerates the npm, Yarn, and uv lockfiles from the combined
manifests instead of resolving generated-file conflicts by selection.
- Rolls overlapping updates forward to one compatible result: pyasn1
0.6.4 supersedes 0.6.3; pyOpenSSL 26.2.0 remains compatible with
cryptography 48.0.1; and Vite 8/Rolldown makes the older Rollup-only
overrides obsolete.
- Retains updates already present on current `main` without
reintroducing stale pins, including Aspire Hosting Azure Search 13.3.0
and Prompty.Core 2.0.0-beta.3.

The full .NET solution builds in Debug with zero warnings and errors.
Focused validation passed 82 .NET tests (3 skipped), 1,096 Python tests,
both frontend production builds, and uv lock consistency checks for the
main Python project and OAuth sample.

### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [ ] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
@moonbox3

Copy link
Copy Markdown
Collaborator

Superseded by #14176

@moonbox3 moonbox3 closed this Jul 23, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/dotnet/samples/Demos/ProcessFrameworkWithSignalR/src/ProcessFramework.Aspire.SignalR.ReactFrontend/multi-bf05dc1ecf branch July 23, 2026 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file. Used by Dependabot. javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants