R4MVC is a Roslyn code generator for ASP.NET Core MVC apps that creates strongly typed helpers that eliminate the use of literal strings in many places
Apache License 2.0
157
stars
48
forks
source link
Extra packages on MyGet being ordered above the latest CI build #74
Could I ask you to remove some of the published packages on MyGet?
During early deployment tests, AppVeyor ended up accidentally deploying some Microsoft.* packages to our MyGet, which we should probably remove.
Also, unfortunately NuGet thinks that 1.0.0-ci-vscommunity-path-00164 is newer than 1.0.0-ci-00190.
We have two "feature" builds on there for each of the packages that end up identified as the "latest" builds.
I've updated the appveyor code so that new feature branch builds will get a double dash before the branch name, putting them below the mainstream CI builds, but could you also remove these two builds from MyGet? (1.0.0-ci-vscommunity-path-00164 and 1.0.0-ci-dotnet-core-2-00158)
Hey @kevinkuszyk,
Could I ask you to remove some of the published packages on MyGet?
During early deployment tests, AppVeyor ended up accidentally deploying some Microsoft.* packages to our MyGet, which we should probably remove.
Also, unfortunately NuGet thinks that
1.0.0-ci-vscommunity-path-00164
is newer than1.0.0-ci-00190
. We have two "feature" builds on there for each of the packages that end up identified as the "latest" builds.I've updated the appveyor code so that new feature branch builds will get a double dash before the branch name, putting them below the mainstream CI builds, but could you also remove these two builds from MyGet? (
1.0.0-ci-vscommunity-path-00164
and1.0.0-ci-dotnet-core-2-00158
)Thanks