Azure / Azure/azure-functions-powershell-worker
Refresh transitive dependencies in PS7.4 worker package
- Dominant language
- C#
- Stars
- 215
- Forks
- 61
- Avg merge
- 21h 4m
- Merged PRs (30d)
- 6
Description
## Summary
The latest published `Microsoft.Azure.Functions.PowerShellWorker.PS7.4` package (`v4.0.4759`, 2026-02-06) carries some transitive dependencies that are now a few patch versions behind their latest releases. It would be great to cut a refreshed PS7.4 build that picks up current patches.
A notable example is `System.Security.Cryptography.Xml`, currently shipped at `8.0.2`. Newer patches are available on the `8.0.x`, `9.0.x`, and `10.0.x` lines.
## Why we're asking
Azure Functions Core Tools bundles the PS7.4 worker package directly. When transitive deps inside the worker fall behind, scans against the published Core Tools artifact (and downstream images such as Cloud Shell) flag them, and we have no way to bump them ourselves without a new worker release.
## Ask
- Refresh transitive deps on the PS7.4 worker (and PS7.6 if it carries the same payload) and publish a new build.
- A periodic cadence for dep refreshes would help us stay clean across the chain (worker → host → Core Tools → Cloud Shell).
Happy to provide more detail or coordinate timing if useful.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names the PS7.4 worker package and published version v4.0.4759, but no repository files or tests. Start by locating the PS7.4 dependency declarations and packaging entry point, then compare the resulting transitive versions with the published package. Done means refreshed PS7.4, and possibly PS7.6, artifacts are built, validated, and published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100