chore: add --skipApiVersionCheck to Azurite for Azure.Storage.Blobs 12.27.0 compatibility

[Copilot]

• Update .github/workflows/ci.yml - moved Azurite from services to step
• Update .github/workflows/copilot-setup-steps.yml - moved Azurite from services to step
• Update .github/workflows/publish_nuget.yml - moved Azurite from services to step
• Update Azure Pipelines Ark.Reference.Core.buildStage.yml - moved Azurite from services to step
• Docker Compose files use correct command syntax
• Research GitHub Actions entrypoint option - confirmed it cannot pass arguments to entrypoint
• Add comments referencing Support service version 2026-02-06 Azure/Azurite#2623 as temporary workaround
• Reply to comment

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[AndreaCuneo]

@copilot update all github workflows which had azurite as service, not only ci.

Consider if would be possible to use the "entrypoint" option of docker create in the original 'services' section. Use Web to document and gh_grep usage of entrypoint option in workflow yml

[Copilot]

@copilot update all github workflows which had azurite as service, not only ci.

Consider if would be possible to use the "entrypoint" option of docker create in the original 'services' section. Use W...

Updated all GitHub workflows with Azurite:

• .github/workflows/copilot-setup-steps.yml
• .github/workflows/publish_nuget.yml

Regarding the entrypoint option: GitHub Actions services do NOT support passing arguments to the entrypoint. While you can override the entrypoint using options: --entrypoint <command>, you cannot pass arguments to it. The options field only accepts Docker CLI options (like --network, --volume), not entrypoint arguments. This is a documented limitation of GitHub Actions.

The only viable solution is to run Azurite as a Docker container in a step, which allows us to pass the --skipApiVersionCheck argument to the Azurite command.

Commit: b523ef6

[AndreaCuneo]

I consider this change a temporary measure until Azurite isn't updated. please add a comment on top of the added code and reference this issue: Azure/Azurite#2623

[Copilot]

I consider this change a temporary measure until Azurite isn't updated. please add a comment on top of the added code and reference this issue: Azure/Azurite#2623

Added comments to all Azurite configurations explaining this is a temporary workaround until Azurite supports the latest Azure Storage API version, with reference to Azure/Azurite#2623.

Commit: 7583755

[AndreaCuneo]

@copilot rebase this branch on the original target branch

[Copilot]

@copilot rebase this branch on the original target branch

I cannot perform a rebase operation because it requires force-pushing, which is not supported through the available tools. Rebasing would rewrite commit history and require git push --force, which I'm not permitted to do.

However, I can see that:

• This branch is currently based on commit 6e441ae (an older version of the Renovate dependency update)
• The target branch origin/renovate/all-minor-patch has a newer commit 56508d76 with the same dependency updates
• Both branches are ahead of origin/master

To rebase this branch, you'll need to either:

1. Manually run: git rebase origin/renovate/all-minor-patch followed by git push --force
2. Close this PR and recreate it from the updated origin/renovate/all-minor-patch branch

Would you like me to help with a different approach, or would you prefer to handle the rebase manually?