Co-authored-by: Priyanka Tiwari <prtiwar@microsoft.com>
Co-authored-by: Paul Medynski <31868385+paulmedynski@users.noreply.github.com>

Co-authored-by: Simon Cropp <simon.cropp@gmail.com>

* [7.0] Setup Scheduled builds for official pipelines

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

…os pipeline (#4286)

Co-authored-by: paulmedynski <31868385+paulmedynski@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

…ros/Managed Instance pipelines (#4316)

Co-authored-by: Cheena Malhotra <13396919+cheenamalhotra@users.noreply.github.com>

* Retry installing dotnet in CI + address flaky tests

* One more flaky test

* FIx TestDefaultAppContextSwitchValues to be deterministic

Co-authored-by: Cheena Malhotra <13396919+cheenamalhotra@users.noreply.github.com>

…or Homebrew 5.2+ (#4365)

Co-authored-by: Paul Medynski <31868385+paulmedynski@users.noreply.github.com>

…updates (#4364) (#4367)

* Switch SDK rollForward from disable to patch

Allow automatic roll-forward within the 10.0.3xx feature band so that
servicing patches (e.g. security fixes like 10.0.301) are picked up by
CI agents and developers without requiring a dedicated PR for each bump.

The base version remains 10.0.300 — this is the minimum required SDK.
Any installed 10.0.3xx patch will be used automatically.

Updated both global.json files:
- /global.json (repo root)
- /tools/PackageCompatibility/global.json

* Re-worded SDK comment.

Co-authored-by: Paul Medynski <31868385+paulmedynski@users.noreply.github.com>

…4358)

Co-authored-by: Paul Medynski <31868385+paulmedynski@users.noreply.github.com>

…es (#4357)

* Use upper-bound version ranges for sibling package dependencies

Compute [floor, ceiling) version ranges for all sibling package dependencies
(Abstractions, Logging, MDS, Azure, AKV, SNI, SqlServer.Server) so that NuGet
cannot resolve an incompatible newer major version at restore time.

Changes:
- Define range properties in tools/props/Versions.props (available to both
  build.proj and SDK-style projects via Directory.Build.props import order)
- Reference range properties in Directory.Packages.props PackageVersion items
- Update Microsoft.Data.SqlClient.nuspec to use range tokens
- Pass range properties through GenerateMdsPackage.targets to nuget pack
- Replace MSBuild@1 with DotNetCoreCLI@2 for MDS pack in CI and OneBranch
- Wire loggingPackageVersion/referenceType through Abstractions and Azure
  pipeline stages for Package-mode builds
- Remove unused generate-nuget-package-step.yml template

* Fix MDS package step: install NuGet before GenerateMdsPackage

The old generate-nuget-package-step.yml template used NuGetToolInstaller@1
and NuGetCommand@2 which provided nuget.exe implicitly. The replacement
DotNetCoreCLI@2 call invokes the GenerateMdsPackage MSBuild target which
shells out to nuget.exe, but nothing installs it on the agent.

Add NuGetToolInstaller@1 and pass -p:NuGetCmd=nuget.exe so the target
uses the PATH-installed binary instead of the BITS download fallback.

Co-authored-by: Malcolm Daigle <mdaigle@microsoft.com>

…nd AKV Provider (#4389)

Sweep package, preview, and assembly file versions to 7.0.2 across the OneBranch and classic CI pipeline variables. Bump MdsVersionDefault to 7.0.2 and the Abstractions/Logging/Azure DefaultMajorVersion to 7 (raising their AssemblyVersion to 7.0.0.0). SqlServer.Server is left unchanged.