12f4235342
Merge branch 'release/2.1' into release/2.2
2018-09-05 17:23:44 -07:00
e9b0415bb9
Make System.IO.Pipelines a direct dependency of Microsoft.AspNetCore.App
2018-09-05 15:20:11 -07:00
cb642ff95f
Update to .NET Core 2.2.0-preview2-26905-02 ( #1377 )
2018-09-05 09:00:01 -07:00
6783427444
Merge branch 'release/2.1' into release/2.2
2018-09-04 11:42:02 -07:00
68672bc965
Update to .NET Core 2.1.5-servicing-26902-03 ( #1371 )
2018-09-04 10:10:31 -07:00
9f37a92dc9
Add Microsoft.AspNetCore.DataProtection.EntityFrameworkCore
2018-08-30 16:28:54 -07:00
b7b1ea207d
Start shipping templates to NuGet
2018-08-30 15:41:16 -07:00
3e7410333a
Update to .NET Core 2.1.5-servicing-26830-03 ( #1364 )
2018-08-30 15:27:17 -07:00
11f28139d4
Add Microsoft.EntityFrameworkCore.SqlServer.NetTopologySuite
2018-08-30 14:27:49 -07:00
6e33b889c0
Unpin System.Data.Sqlient ( #1356 )
2018-08-30 08:33:05 -07:00
820c0405e3
Add new options package ( #1345 )
2018-08-29 10:41:54 -07:00
65ddfd1f02
Add dotnet-httprepl to artifacts.props
2018-08-28 15:11:25 -07:00
b206d59612
Prepare 2.1.5 patch
2018-08-28 09:14:43 -07:00
d9d2130639
Update Microsoft.DotNet.Build.Tasks.Feed to 2.2.0-preview1-03124-01 and increase timeout to 10 minutes
2018-08-24 10:59:36 -07:00
12e2d30f6b
Publish .jar files to ProdCon output
2018-08-22 19:08:17 -07:00
84c8c61d79
Remove temporary exclusion to output path adjustments
2018-08-20 16:29:59 -07:00
d93aded1c0
Remove package version from the output path for shared runtime archives
2018-08-20 16:27:48 -07:00
28d4064cba
Add a build definition for compiling Universe in VSTS
2018-08-20 16:02:43 -07:00
b67a141263
Add code for building the Windows Hosting Bundle and ASP.NET Core runtime installers into this repo
...
This code previously was in private repos because it had references to internal locations and drop shares. This code has been modified to remove these internal-only pieces.
2018-08-20 15:56:22 -07:00
2560815501
Add NetTopologySuite external dependency
2018-08-20 11:30:05 -07:00
86b7d5162a
Merge branch 'release/2.1' into release/2.2
2018-08-20 08:28:58 -07:00
5bae8c768d
Fix publishing targets to correctly reference the right item group: NpmPackageToPublish
2018-08-17 15:20:05 -07:00
4b1e0d09c7
Skip npm package publishing if there are no npm packages to release
2018-08-17 11:34:22 -07:00
a988e9898d
Merge branch 'release/2.1' into release/2.2
2018-08-16 16:51:24 -07:00
267b149bc8
Fix whitespace in task parameters ( #1322 )
...
In MSBuild 15.8, whitespace in task parameters is handled differently in a way that causes these docker commands to fail.
2018-08-16 16:48:08 -07:00
d3f51da519
Add EFCore.Cosmos.Sql to shipping package list
2018-08-15 14:28:02 -07:00
ac9b1f97c5
Add a restore feed for 2.1.3 packages
2018-08-10 10:02:45 -07:00
ecb353ab2a
Merge branch 'release/2.1' into release/2.2
2018-08-10 09:49:37 -07:00
555f10b5f9
Fix #650 - remove the BuildGraphOf property ( #1302 )
2018-08-10 09:42:43 -07:00
a85d99ab8e
Add the 2.1.3 archive baselines and a target to ensure this test is run on PR builds
2018-08-10 09:08:55 -07:00
e4161d8971
Prepare 2.1.4 patch
...
* Update submodules for EF Core, Scaffolding, and Templating
* Change version number for metapackages to 2.1.4
2018-08-07 21:24:01 +00:00
c0ed5c71a4
Add Microsoft.AspNetCore.Mvc.Api.Analyzers
2018-08-02 13:53:12 -07:00
165c712201
Use OSS package versions consistent with aspnet/benchmarks and Microsoft.AspNetcore.All 2.1.2
...
- update our own NuGet packages to align lower-level dependencies
2018-08-01 11:14:10 -07:00
232c71f772
React to removing .Buffers.Sources package
2018-07-26 09:32:43 -07:00
0b85431980
React to renaming the WebHostBuilderFactory source package
2018-07-25 16:52:21 -07:00
06f0146731
Merge branch 'release/2.1' into release/2.2
2018-07-25 11:10:03 -07:00
7119fc7e1d
Upgrade xunit test runner to 2.4.0 RTM and xunit.analyzers to 0.10.0 ( #1275 )
...
Also, cleaned up two unused properties from the deps.props file.
2018-07-25 11:08:35 -07:00
2d79bee072
Remove condition on the Server.IIS package
2018-07-25 09:40:43 -07:00
2e96271e69
Merge branch 'release/2.1' into release/2.2
2018-07-25 09:29:48 -07:00
aee905e359
Sort list of artifacts and add selenium to external artifacts
2018-07-25 09:18:53 -07:00
18e0871fe2
Update to NETCore.App 2.1.3-servicing-26722-02
2018-07-23 19:40:41 -07:00
7d12e6bb13
Updating external dependencies ( #1268 )
...
New versions:
MicrosoftNETCoreDotNetAppHostPackageVersion
MicrosoftNETCoreAppPackageVersion
2018-07-19 17:31:53 -07:00
8260ed6c46
Update to NETCore.App 2.1.3-servicing-26718-02
2018-07-18 19:47:18 -07:00
019210ff0a
Fix for when InstallSharedRuntimeFromPreviousBuild is true and AspNetCoreFxFeed is set
2018-07-18 11:20:23 -07:00
b5be7b56d9
Add Microsoft.AspNetCore.Server.IIS to metapackges ( #1263 )
2018-07-17 09:21:32 -07:00
7c6a60b62b
EFCore: Upgrade IX-Async
2018-07-16 15:28:34 -07:00
b144f3a12f
Update artifacts.props
2018-07-13 14:16:05 -07:00
3af5287b66
Make HealthChecks back into shipping packages
2018-07-13 14:16:05 -07:00
e69a47f230
Implement patch policies per repo and set default to ProductChangesOnly
...
Our policy since 1.0.0 has been to always cascade version updates in the packages we own. e.g. if Logging has a product change in 2.1.x, then Kestrel, EF Core, Mvc, etc also re-ship with the updated Logging dependency. This has been done for a variety of reasons:
* NuGet does not show updates for transitive dependencies, only direct ones
* NuGet does resolves the lowest compatible transitive dependencies
* ASP.NET Core ships to both .NET Framework (where transitive dependency version matters) and .NET Core (where it matters less if you use the shared framework)
While transitive dependencies is still an important scenario, this practice of always patching has led to bigger issues.
* High probability users will unintentionally upgrade out of the shared framework: #3307
* Conflicts with metapackages that attempt to use exact version constraints: aspnet/Universe#1180
* A quality perception issue: the high volume of new versions in servicing updates with only metadata changes has created the impression that new versions of packages may not be very important. It's also made it appear like there are more issues product than there really are.
* High volume of packages changing with only metadata changes. Of the last 301 packages published in a servicing update, only 11 contained actual changes to the implementation assemblies. (3.5%)
This change implements a system to verify a new, non-cascading versioning policy for servicing updates. This required changes to repos to pin version variables to that matter per-repo,
and to remove some of the restrictions and checks.
Incidentally, this should make defining new patches easier because it automatically determines which packages are or are not patching in the release.
2018-07-12 21:33:50 -07:00
3042728f8b
Add Microsoft.AspNetCore.Server.IntegrationTesting.IIS ( #1253 )
2018-07-12 11:56:44 -07:00
Nate McMaster
dotnet-maestro-bot
Ryan Brandenburg
Brice Lambson
Matt Mitchell
Hao Kung
Nate McMaster
Smit Patel
Pranav K
Doug Bunting
Pavel Krymets
Ryan Nowak