-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Update buildtools to 3.0.0-build-20190123.3 #6959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
version:3.0.0-build-20190122.3 | ||
commithash:43e5fa8e3d8b192e573c3c14ae39b43e1d05cd5e | ||
version:3.0.0-build-20190123.3 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ick. Is there any way to propagate this version from a single source of truth (preferably this file)? Annoying to need to change multiple locations. Or, please point me to the script which does the needful 😸 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I usually do this:
That re-generates korebuild-lock.txt and global.json. Then, I manually update eng/Versions.props to match. The version in eng/Versions.props is only there to make Visual Studio happy. Command-line builds are always in-sync with the version in korebuild-lock.txt. We could get rid of eng/Versions.props by replacing the PackageReference to Internal.AspNetCore.Sdk with a proper 'MSBuild Sdk', but that's not something I want to tackle just yet. |
||
commithash:bfcdf8474c79320b7e5edcdb33d94bbdccb41e32 |
Uh oh!
There was an error while loading. Please reload this page.