[Release] Milestone M193 #1807
Merged
[Release] Milestone M193 #1807
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version allows us to update existing `winget` manifests by specifying a manifest's SHA if it already exists in `microsoft/winget-pkgs`. Pull Requests --------------- * [#178](mjcheetham/update-winget#179): Allow updates to existing winget manifests
Upgrade `update-winget` action to v1.4
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Co-authored-by: Victoria Dye <vdye@github.com>
The recommended way to install is now to use `winget`.
Updating necessary files to support spaces in paths when compiling VFS for Git.
Updating inno installer metadata to align with the specification outlined in github/git-fundamentals#700.
`wingetcreate` is a Windows exe and thus must be run on Windows. Updating our release-winget workflow accordingly.
Set up infrastructure for `wingetcreate`
Adding the source parameter will make sure that the install command will actually install from winget
…s in msstore To address this: using the id parameter we can make sure it will always install this package.
These are verified by the Scalar functional tests, anyway.
There were some build issues related to the install path moving from "GVFS" to "VFS for Git". The pack-file maintenance tests were flaky for reasons we've seen before on the Scalar side, so let's focus our efforts keeping the Scalar tests green.
Remove the custom mjcheetham/update-winget task in favor of the wingetcreate tool.
Deploy to winget via wingetcreate
…ng to pass on pass-fail information to future instances
Use index.lock and move writes to head and refs to the end of the run to make interrupted fastfetch operations less bad
Necessary for new singing build changes.
*.csproj: update MicroBuild package names
The Nuget.Commmands package version 4.9.2 contains a known vulnerability. Fortunately we are no longer using this package and can mitigate by removing our reference to it.
Update newtonsoft.json to 13.0.1 to mitigate exposure to security vulnerability associated with previous versions.
Update newtonsoft.json to 13.0.1 to mitigate exposure to security vulnerability associated with previous versions.
dependencies: resolve dependabot alerts
UtcNow spends a lot of time getting a very precise system time, including leap seconds and interpolation through QueryPerformanceCounter. Use Environment.TickCount (milliseconds since boot) instead, since that just retrieves a value in shared memory that the kernel keeps up to date. This value is still suitable for controlling how much log output index parsing produces. This UtcNow call consumes 15% of the time under GitIndexParser.ParseIndex. See https://github.com/dotnet/runtime/blob/master/src/libraries/System.Private.CoreLib/src/System/DateTime.Windows.cs.
…ount index-parser: get the time in a cheaper way
To more rapidly adopt OAuth tokens, set that as the default for GVFS repos. This will update on mount, so all users will update to this mode when they upgrade to a version including this commit. This may cause some initial frustration as the first time I ran a fetch in OAuth mode my local clone had a failure with GCM and defaulted to username/password checks over command line. The second fetch worked just fine, though.
fix: #1802 confirm cached credential before rejecting
mjcheetham
approved these changes
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This includes the fix in #1803 as well as other changes made since the last release.
Pull requests by topic
Bugfixes
Winget
update-wingetaction to v1.4 #1753wingetcreate#1755Enhancements
Miscellaneous