Repository navigation
Dependency updates: merge as soon as build passes, one NUnit version, fast-uri security fix (version 0.4.6) - #52
Merged
Conversation
…the NUnit version (version 0.4.6)
Merged
This file contains hidden or 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
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.
Task 4f follow-up.
workflow_runon Build, dispatched runs only). If that build passed it merges the update straight away and moves on to the next one; if it failed it holds the update and moves on. Before, the next step waited for the hourly run, which GitHub hadn't fired once in the hour since it was added.src/Directory.Build.props(for every test project) and inRequestarr.Test.Common. Dependabot only updates the second, so Backend packages: Bump the backend group with 12 updates #49 failed with a package downgrade. It now comes only fromRequestarr.Test.Common, which every test project that uses it references.yarn.lock(build tooling only, nothing shipped), which fixes Dependabot alerts 10 to 13. Dependabot hadn't opened its own security PR.docs/development.md#dependency-updatesupdated.Version 0.4.6, heading only (nothing a user or admin sees).
Tests: solution build 0 warnings; Common 682 passed, 0 failed, 14 skipped; Core 1,023 passed, 0 failed, 3 skipped; update script self-test 17 of 17.