KEMBAR78
Show Recommended Actions in Error Concise View by JustinGrote · Pull Request #20826 · PowerShell/PowerShell · GitHub
Skip to content

Conversation

@JustinGrote
Copy link
Contributor

@JustinGrote JustinGrote commented Dec 1, 2023

CC @SteveL-MSFT per previous discussion.

PR Summary

Exposes the RecommendedAction in an ErrorRecord to ConciseView

❯ write-Error 'oops' -RecommendedAction 'You should fix the oops'
Write-Error: oops
  Recommendation: You should fix the oops

PR Context

If an ErrorRecord Author has gone to the trouble to define RecommendedAction, we should expose this to the user at the time of the Error to help guide them to a solution. This makes the most sense in the default ConciseView as that is where most new users are likely to see it.

This could be done with a Feedback Provider (and I have implemented one for example) but I think it makes more sense as a core message, especially as the users who will best benefit from this information are likely to be new users who don't even know what a Feedback Provider is much less enabling one, so having it default into ConciseView makes a lot of sense.

There is a potential breaking change here in cases where users are matching errors exactly say on text output of a pwsh process. While that is obviously discouraged it must be considered, however as the team previously switched the default ErrorView to ConciseView from NormalView as the default, it is assumed the team has an appetite for this type of change.

PR Checklist

@JustinGrote JustinGrote changed the title Feature/conciseViewRecommendedAction Show Recommended Actions in Error Concise View Dec 1, 2023
@pull-request-quantifier-deprecated

This PR has 9 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +8 -1
Percentile : 3.6%

Total files changed: 2

Change summary by file extension:
.cs : +4 -1
.ps1 : +4 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@JustinGrote
Copy link
Contributor Author

JustinGrote commented Dec 1, 2023

One thought: Does Recommendation need to be localized? How exactly would we do that? Or should we remove Recommendation: entirely and just show the recommendation on the indented line?

@kilasuit kilasuit added WG-Interactive-Debugging debugging PowerShell script WG-NeedsReview Needs a review by the labeled Working Group labels Dec 4, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Dec 11, 2023
@JustinGrote
Copy link
Contributor Author

@kilasuit 1.5 month follow up now that we are after the break. Can this get on the docket for Interactive WG? Thanks.

@kilasuit
Copy link
Collaborator

@JustinGrote have mentioned it to the rest of the WG so hopefully this'll get looked at soon

Copy link
Collaborator

@JamesWTruher JamesWTruher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@theJasonHelmick theJasonHelmick removed the WG-NeedsReview Needs a review by the labeled Working Group label Jan 17, 2024
@theJasonHelmick
Copy link
Collaborator

Thank you @JustinGrote for this PR. The Interactive WG agrees that this behavior is beneficial.

@JustinGrote
Copy link
Contributor Author

PowerShell-CI-Windows build failures do not appear to be related to this module, recommend a rebase once whatever is causing it is fixed.

@JustinGrote
Copy link
Contributor Author

@theJasonHelmick what more needs to be done to get this merged? I have no outstanding work items.

@theJasonHelmick
Copy link
Collaborator

Hi @JustinGrote! The WG liked the direction and agreed that this would be beneficial to add. You are most welcome to make the pr :).

@JustinGrote
Copy link
Contributor Author

@theJasonHelmick....uh...this IS the PR....

@theJasonHelmick
Copy link
Collaborator

@JustinGrote - Doh! Thats what happens when I'm working issues early on a Monday :). My apologies for the mistake. I'll raise with @SteveL-MSFT and the committee. -- cheers!

@theJasonHelmick theJasonHelmick added the Review - Committee The PR/Issue needs a review from the PowerShell Committee label Feb 5, 2024
@SteveL-MSFT SteveL-MSFT removed the Review - Committee The PR/Issue needs a review from the PowerShell Committee label Feb 7, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Feb 7, 2024
@pull-request-quantifier-deprecated

This PR has 9 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +8 -1
Percentile : 3.6%

Total files changed: 2

Change summary by file extension:
.cs : +4 -1
.ps1 : +4 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT Hi Steve, friendly weekly follow up, this has passed all approvals and has passed all tests and should meet all requirements to be merged. Do the merges happen after a final meeting or something?

@StevenBucher98 StevenBucher98 added the CommunityDay-Small A small PR that the PS team has identified to prioritize to review label Feb 14, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Feb 22, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Mar 4, 2024
@SteveL-MSFT
Copy link
Member

@JustinGrote can you resolve the merge conflict?

@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT wasn't aware there was one, can do.

@JustinGrote JustinGrote force-pushed the feature/conciseViewRecommendedAction branch 2 times, most recently from ee017b0 to 1d46720 Compare March 5, 2024 16:07
@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT it was introduced by @SeeminglyScience like practically minutes prior to the review :). It's been fixed.

@pull-request-quantifier-deprecated

This PR has 67 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Small
Size       : +35 -32
Percentile : 26.8%

Total files changed: 2

Change summary by file extension:
.cs : +4 -1
.ps1 : +31 -31

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

1 similar comment
@pull-request-quantifier-deprecated

This PR has 67 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Small
Size       : +35 -32
Percentile : 26.8%

Total files changed: 2

Change summary by file extension:
.cs : +4 -1
.ps1 : +31 -31

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@JustinGrote
Copy link
Contributor Author

Failed flaky MacOS tests not related to this PR. Linux test passes fine.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Mar 12, 2024
@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT Should be good to go.

@SteveL-MSFT
Copy link
Member

@JustinGrote can you rebase against master? Some of the failures have been addressed already in master branch

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Apr 1, 2024
@JustinGrote JustinGrote force-pushed the feature/conciseViewRecommendedAction branch from 1d46720 to b28e788 Compare April 2, 2024 00:04
@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT done, it looks like you need to re-approve the new macos tests
image

@JustinGrote
Copy link
Contributor Author

@SteveL-MSFT current MacOS test failure still not related:
image

@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Apr 9, 2024
@daxian-dbw daxian-dbw merged commit 7ad4329 into PowerShell:master Apr 15, 2024
@daxian-dbw daxian-dbw added the CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log label Apr 15, 2024
@microsoft-github-policy-service
Copy link
Contributor

📣 Hey @JustinGrote, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Review - Needed The PR is being reviewed label Apr 15, 2024
@JustinGrote
Copy link
Contributor Author

@daxian-dbw Thank you! I'll test the buid tomorrow to look for any annoying issues.

@JustinGrote JustinGrote deleted the feature/conciseViewRecommendedAction branch April 15, 2024 18:03
imatthewtanner added a commit to tannerpresscorp/PowerShell that referenced this pull request May 28, 2024
* Bump xunit from 2.6.3 to 2.6.4 (PowerShell#20967)

Bumps [xunit](https://github.com/xunit/xunit) from 2.6.3 to 2.6.4.
- [Commits](xunit/xunit@2.6.3...2.6.4)

---
updated-dependencies:
- dependency-name: xunit
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump xunit.runner.visualstudio from 2.5.5 to 2.5.6 (PowerShell#20966)

Bumps [xunit.runner.visualstudio](https://github.com/xunit/visualstudio.xunit) from 2.5.5 to 2.5.6.
- [Release notes](https://github.com/xunit/visualstudio.xunit/releases)
- [Commits](xunit/visualstudio.xunit@2.5.5...2.5.6)

---
updated-dependencies:
- dependency-name: xunit.runner.visualstudio
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add Import-LocalizedData implicit Localization fallback (PowerShell#19896)

* Adds culture fallback to Import-LocalizedData

* Only add fallback if current culture is not en-US

* Pester 4 compatibility

* Missing param block in It

* Missed param block for It

* Skip UICulture name test for Linux and Mac

* Removed test fragment

* Fix typo in remotingexceptions.cs (PowerShell#21015)

formating -> formatting

* Fix failures in GitHub action `markdown-link-check` (PowerShell#20996)

* Bump xunit from 2.6.4 to 2.6.5 (PowerShell#21008)

* Include information about upgrading in README (PowerShell#20993)

* Update the cgmanifest (PowerShell#20955)

* Add `Aliases` to the properties shown up when formatting the help content of the parameter returned by `Get-Help` (PowerShell#20994)

* Bump JsonSchema.Net from 5.4.2 to 5.5.0 (PowerShell#21027)

* Fix regression -Tail 0 -Wait (PowerShell#20734)

* Update README.md and metadata.json for v7.2.18 and v7.4.1 releases (PowerShell#21044)

* Update changelog for v7.2 and v7.3 (PowerShell#21052)

* Bump xunit from 2.6.5 to 2.6.6 (PowerShell#21071)

* Bump StyleCop.Analyzers from 1.2.0-beta.507 to 1.2.0-beta.556 (PowerShell#20953)

* Update to the latest NOTICES file (PowerShell#20905)

* Update the cgmanifest (PowerShell#21047)

* Fix completion crash for the SCCM provider (PowerShell#20915)

* Bump .NET SDK to 8.0.101 (PowerShell#21084)

* Add `WinGetCommandNotFound` and `CompletionPredictor` modules to track usage (PowerShell#21040)

* Merged PR 29314: Update ChangeLog for v7.5.0-preview.1

Update ChangeLog for v7.5.0-preview.1

* Update `README.md` and `metadata.json` for v7.5.0-preview.1 release (PowerShell#21094)

* Fix Get-Error serialization of array values (PowerShell#21085)

Ensure Get-Error does not hang when attempting to serialize an exception
that contains a property whose type is an array of System.Type
instances. Also ensures that primitive types like System.Int32,
System.Boolean as well as System.String is formatted as a string rather
than an object with properties.

* Validate the value for `using namespace` during semantic checks to prevent declaring invalid namespaces (PowerShell#21162)

* Fix `using assembly` to use `Path.Combine` when constructing assembly paths (PowerShell#21169)

* Add `DirectoryInfo` to the `OutputType` for `New-Item` (PowerShell#21126)

* Bump JsonSchema.Net to v5.5.1 (PowerShell#21120)

* Update changelog for v7.4.1 (PowerShell#21098)

* Update WG members (PowerShell#21091)

* Update the cgmanifest (PowerShell#21093)

* Fix incorrect examples in XML docs in `PowerShell.cs` (PowerShell#21173)

* Generate MSI for `win-arm64` installer (PowerShell#20516)

* Rewrite the mac syslog tests to make them less flaky (PowerShell#21174)

* Update versions of PSResourceGet (PowerShell#21190)

* Add tilde expansion for windows native executables (PowerShell#20402)

* Bump XunitXml.TestLogger from 3.1.17 to 3.1.20 (PowerShell#21207)

* Remove `PSScheduledJob` module source code (PowerShell#21189)

* Update to the latest NOTICES file (PowerShell#21177)

* Update the cgmanifest (PowerShell#21178)

* Fix a typo in `CoreAdapter.cs` (PowerShell#21179)

* ConvertFrom-Json: Add -DateKind parameter (PowerShell#20925)

Adds the -DateKind parameter to the ConvertFrom-Json that allows the
caller to control how DateTime strings are converted into an object. The
default behaviour is to create a DateTime value with the Kind being
Unspecified if no TZ is set, Utc if the TZ Z is set, Local (after
conversion) if an explicit TZ is set. This adds a Utc, Local to
explicitly set the Kind as desired as well as a Offset and String value
to create a DateTimeOffset or keep as a string.

* Bump Microsoft.NET.Test.Sdk from 17.8.0 to 17.9.0

Bumps [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest) from 17.8.0 to 17.9.0.
- [Release notes](https://github.com/microsoft/vstest/releases)
- [Changelog](https://github.com/microsoft/vstest/blob/main/docs/releases.md)
- [Commits](microsoft/vstest@v17.8.0...v17.9.0)

---
updated-dependencies:
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update dependabot.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Create codeql.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Bump the nuget group across 1 directories with 1 update

Bumps the nuget group with 1 update in the /test/tools/TestAlc/nested directory: [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json).


Updates `Newtonsoft.Json` from 10.0.1 to 13.0.1
- [Release notes](https://github.com/JamesNK/Newtonsoft.Json/releases)
- [Commits](JamesNK/Newtonsoft.Json@10.0.1...13.0.1)

---
updated-dependencies:
- dependency-name: Newtonsoft.Json
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump PowerShellGet from 2.2.5 to 2.2.5.1 in /src/Modules

Bumps [PowerShellGet](https://github.com/PowerShell/PowerShellGet) from 2.2.5 to 2.2.5.1.
- [Changelog](https://github.com/PowerShell/PowerShellGet/blob/master/CHANGELOG.md)
- [Commits](https://github.com/PowerShell/PowerShellGet/commits)

---
updated-dependencies:
- dependency-name: PowerShellGet
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump to .NET 9 Preview 1 (PowerShell#21229)

* Update the cgmanifest (PowerShell#21237)

* Update to the latest NOTICES file (PowerShell#21236)

* Update experimental-feature json files (PowerShell#21213)

* Remove `surrogateFile` setting of APIScan (PowerShell#21238)

* Add dotenv install as latest version does not work with current Ruby version (PowerShell#21239)

* Bump xunit from 2.6.6 to 2.7.0

Bumps [xunit](https://github.com/xunit/xunit) from 2.6.6 to 2.7.0.
- [Commits](xunit/xunit@2.6.6...2.7.0)

---
updated-dependencies:
- dependency-name: xunit
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump xunit.runner.visualstudio from 2.5.6 to 2.5.7

Bumps [xunit.runner.visualstudio](https://github.com/xunit/visualstudio.xunit) from 2.5.6 to 2.5.7.
- [Release notes](https://github.com/xunit/visualstudio.xunit/releases)
- [Commits](xunit/visualstudio.xunit@2.5.6...2.5.7)

---
updated-dependencies:
- dependency-name: xunit.runner.visualstudio
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Add dotnet-runtime-9.0 as a dependency for the Mariner package (PowerShell#21259)

* Adding WG membership template (PowerShell#21153)

* Adding WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Editing WG membership template

* Update .github/ISSUE_TEMPLATE/WG_member_request.yaml

Co-authored-by: Steve Lee <slee@microsoft.com>

* Update .github/ISSUE_TEMPLATE/WG_member_request.yaml

Co-authored-by: Steve Lee <slee@microsoft.com>

---------

Co-authored-by: Jason.Helmick <jahelmic@microsoft.com>
Co-authored-by: Steve Lee <slee@microsoft.com>

* Update `metadata.json` and `README.md` (PowerShell#21264)

* Skip test on Windows Server 2012 R2 for `no-nl` (PowerShell#21265)

* Fix a regression in `Format-Table` when header label is empty (PowerShell#21156)

* Revert "Adjust PUT method behavior to POST one for default content type in WebCmdlets" (PowerShell#21049)

* Fix the regression when doing type inference for `$_` (PowerShell#21223)

* ConvertTo-Json: Serialize `BigInteger` as a number (PowerShell#21000)

* Remove `JetBrains.Annotations` attributes (PowerShell#21246)

* Suppress MacOS package manager output (PowerShell#21244)

* Enable CA1868: Unnecessary call to 'Contains' for sets (PowerShell#21165)

https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1868

* Bump Microsoft.CodeAnalysis.CSharp from 4.8.0 to 4.9.2

Bumps [Microsoft.CodeAnalysis.CSharp](https://github.com/dotnet/roslyn) from 4.8.0 to 4.9.2.
- [Release notes](https://github.com/dotnet/roslyn/releases)
- [Changelog](https://github.com/dotnet/roslyn/blob/main/docs/Breaking%20API%20Changes.md)
- [Commits](https://github.com/dotnet/roslyn/commits)

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.CSharp
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump Microsoft.CodeAnalysis.Analyzers (PowerShell#21297)

* Bump Microsoft.CodeAnalysis.CSharp from 4.9.0-3.final to 4.9.2 (PowerShell#21298)

* Fix error formatting for pipeline enumeration exceptions (PowerShell#20211)

* Fall back to type inference when hashtable key value cannot be retrieved from safe expression (PowerShell#21184)

* Get-Process: Remove admin requirement for `-IncludeUserName` (PowerShell#21302)

* Bump Microsoft.CodeAnalysis.Analyzers (PowerShell#21305)

* Fix a typo in `releaseTools.psm1` (PowerShell#21306)

* Fix PowerShell class to support deriving from an abstract class with abstract properties (PowerShell#21331)

* Handle the case that `Runspace.DefaultRunspace is null` when logging for WDAC Audit (PowerShell#21344)

* Make sure both stdout and stderr can be redirected from a native executable (PowerShell#20997)

* Fix typo in ast.cs (PowerShell#21350)

statment -> statement

* Make sure the assembly/library resolvers are registered at early stage (PowerShell#21361)

* Revert the PR PowerShell#17856 (Do not preserve temporary results when no need to do so) (PowerShell#21368)

* Add file description to `pwsh.exe` (PowerShell#21352)

* PowerShell co-ordinated build OneBranch pipeline (PowerShell#21364)

* Fix argument passing in `GlobalToolShim` (PowerShell#21333)

* Fix build failure due to missing reference in `GlobalToolShim.cs` (PowerShell#21388)

* Fix typo in a test (PowerShell#21337)

connectiong -> connecting

* Fix `Test-Path -IsValid` to check for invalid path and filename characters (PowerShell#21358)

* Fix typo in SessionStateCmdletAPIs.cs (PowerShell#21413)

hte -> the

* Update `PSReadLine` to `v2.3.5` for the next `v7.4.x` servicing release (PowerShell#21414)

* Multiple fixes in official build pipeline (PowerShell#21408)

* Add back two transitive dependency packages (PowerShell#21415)

* Verify environment variable for OneBranch before we try to copy (PowerShell#21441)

* Update PSResourceGet version from 1.0.2 to 1.0.4.1 (PowerShell#21439)

* fix package build to not check some files for a signature. (PowerShell#21458)

* Update `metadata.json` and `README.md` (PowerShell#21454)

* Fix grammar in FAQ.md (PowerShell#21468)

Fix grammar in docs FAQ

* Update CHANGELOG for v7.2.19, v7.3.12 and v7.4.2 (PowerShell#21462)

* Fix the error when using `Start-Process -Credential` without the admin privilege (PowerShell#21393)

* Add `RecommendedAction` to `ConciseView` of the error reporting (PowerShell#20826)

* Update Engine & Interactive-UX Working Group Member lists (PowerShell#20991)

* Bump `Microsoft.CodeAnalysis.Analyzers` (PowerShell#21449)

* Don't complete parameter name and class member declarations (PowerShell#21182)

* Update the doc about how to build PowerShell (PowerShell#21334)

* [StepSecurity] Apply security best practices (PowerShell#21480)

* [StepSecurity] Apply security best practices

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>

* Update dependabot.yml

* Delete tools/releaseBuild/Images/microsoft_powershell_centos7 directory

* Delete tools/releaseBuild/Images/microsoft_powershell_ubuntu16.04 directory

* Delete tools/releaseBuild/Images/microsoft_powershell_ubuntu18.04 directory

* Delete tools/releaseBuild/Images/microsoft_powershell_windowsservercore/Dockerfile

---------

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>

* Bump ossf/scorecard-action from 2.0.6 to 2.3.1 (PowerShell#21485)

* Bump ossf/scorecard-action from 2.0.6 to 2.3.1

Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.0.6 to 2.3.1.
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](ossf/scorecard-action@99c5375...0864cf1)

---
updated-dependencies:
- dependency-name: ossf/scorecard-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update windows.yml

* Update linux.yml

* Update windows.yml

* Update mac.yml

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>

* Bump actions/upload-artifact from 3.1.3 to 4.3.2 (PowerShell#21501)

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.3 to 4.3.2.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@a8a3f3a...1746f4a)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump github/codeql-action from 2.25.0 to 3.25.1 (PowerShell#21498)

Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2.25.0 to 3.25.1.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@v2.25.0...c7f9125)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump actions/checkout from 3.6.0 to 4.1.2 (PowerShell#21482)

Bumps [actions/checkout](https://github.com/actions/checkout) from 3.6.0 to 4.1.2.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v3.6.0...9bb5618)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump actions/dependency-review-action from 2.5.1 to 4.2.5 (PowerShell#21484)

Bumps [actions/dependency-review-action](https://github.com/actions/dependency-review-action) from 2.5.1 to 4.2.5.
- [Release notes](https://github.com/actions/dependency-review-action/releases)
- [Commits](actions/dependency-review-action@0efb1d1...5bbc3ba)

---
updated-dependencies:
- dependency-name: actions/dependency-review-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add a PAT for fetching PMC cli (PowerShell#21503)

* Use new pat

* remove trailing whitespaces

* Fix `[semver]` type to pass semver.org tests (PowerShell#21401)

* Fix `[semver]` type to pass semver.org tests

* fix test to split per OS specific newline

* replace all regex with semver.org ones adding new one for build label, update tests

---------

Co-authored-by: Steve Lee (POWERSHELL HE/HIM) (from Dev Box) <slee@ntdev.microsoft.com>

* Separate DSC configuration parser check for ARM processor (PowerShell#21395)

* Official PowerShell Package pipeline (PowerShell#21504)

* Revert to version available on `Nuget` for `Microsoft.CodeAnalysis.Analyzers` (PowerShell#21515)

* Use correct signing certificates for RPM and DEBs (PowerShell#21522)

* Add branch counter variables for daily package builds (PowerShell#21523)

* Expand `~` to `$home` on Windows with tab completion (PowerShell#21529)

* Bump github/codeql-action from 3.25.1 to 3.25.3

Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.25.1 to 3.25.3.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@c7f9125...d39d31e)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump actions/checkout from 4.1.2 to 4.1.4

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.2 to 4.1.4.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@9bb5618...0ad4b8f)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump actions/upload-artifact from 4.3.2 to 4.3.3

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.3.2 to 4.3.3.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@1746f4a...6546280)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump super-linter/super-linter from 5.7.2 to 6.4.1

Bumps [super-linter/super-linter](https://github.com/super-linter/super-linter) from 5.7.2 to 6.4.1.
- [Release notes](https://github.com/super-linter/super-linter/releases)
- [Changelog](https://github.com/super-linter/super-linter/blob/main/CHANGELOG.md)
- [Commits](super-linter/super-linter@a8150b4...4758be6)

---
updated-dependencies:
- dependency-name: super-linter/super-linter
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* Delete .github/workflows/codeql-analysis.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Update codeql.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Update codeql.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Delete .github/workflows/codeql.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Bump actions/dependency-review-action from 4.2.5 to 4.3.2

Bumps [actions/dependency-review-action](https://github.com/actions/dependency-review-action) from 4.2.5 to 4.3.2.
- [Release notes](https://github.com/actions/dependency-review-action/releases)
- [Commits](actions/dependency-review-action@5bbc3ba...0c155c5)

---
updated-dependencies:
- dependency-name: actions/dependency-review-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* update wix package install (PowerShell#21537)

* Create the Windows.x64 global tool with shim for signing (PowerShell#21559)

* Fix generating `OutputType` when running in Constrained Language Mode (PowerShell#21605)

* Use PSScriptRoot to find path to Wix module (PowerShell#21611)

* Bump actions/checkout from 4.1.4 to 4.1.5

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.4 to 4.1.5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@0ad4b8f...44c2b7a)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Remember installation options and used them to initialize options for the next installation (PowerShell#20420)

* Bump github/codeql-action from 3.25.3 to 3.25.4

Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.25.3 to 3.25.4.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@d39d31e...ccf74c9)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Bump to .NET 9 preview 3 (PowerShell#21782)

* Bump ossf/scorecard-action from 2.3.1 to 2.3.3

Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.3.1 to 2.3.3.
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](ossf/scorecard-action@0864cf1...dc50aa9)

---
updated-dependencies:
- dependency-name: ossf/scorecard-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Use feed with Microsoft Wix toolset (PowerShell#21651)

* Create codeql.yml

Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>

* Bump super-linter/super-linter from 6.4.1 to 6.5.0

Bumps [super-linter/super-linter](https://github.com/super-linter/super-linter) from 6.4.1 to 6.5.0.
- [Release notes](https://github.com/super-linter/super-linter/releases)
- [Changelog](https://github.com/super-linter/super-linter/blob/main/CHANGELOG.md)
- [Commits](super-linter/super-linter@4758be6...56576d4)

---
updated-dependencies:
- dependency-name: super-linter/super-linter
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Matthew Tanner <imatthewtanner@icloud.com>
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Chris Dent <134605137+chrisdent-de@users.noreply.github.com>
Co-authored-by: Ikko Eltociear Ashimine <eltociear@gmail.com>
Co-authored-by: James Truher [MSFT] <jimtru@microsoft.com>
Co-authored-by: Steven Bucher <stevenbucher8@gmail.com>
Co-authored-by: PowerShell Team Bot <69177312+pwshBot@users.noreply.github.com>
Co-authored-by: Dongbo Wang <dongbow@microsoft.com>
Co-authored-by: CarloToso <105941898+CarloToso@users.noreply.github.com>
Co-authored-by: MartinGC94 <42123497+MartinGC94@users.noreply.github.com>
Co-authored-by: Jordan Borean <jborean93@gmail.com>
Co-authored-by: Greg Dennis <gregsdennis@yahoo.com>
Co-authored-by: Patrick Meinecke <SeeminglyScience@users.noreply.github.com>
Co-authored-by: Anam Navied <anam.naviyou@gmail.com>
Co-authored-by: alerickson <25858831+alerickson@users.noreply.github.com>
Co-authored-by: Dom Slee <domslee1@gmail.com>
Co-authored-by: Steve Lee <slee@microsoft.com>
Co-authored-by: Aditya Patwardhan <adityap@microsoft.com>
Co-authored-by: Jason Helmick <jason.helmick@microsoft.com>
Co-authored-by: Jason.Helmick <jahelmic@microsoft.com>
Co-authored-by: xtqqczze <45661989+xtqqczze@users.noreply.github.com>
Co-authored-by: Friedrich von Never <friedrich@fornever.me>
Co-authored-by: guangwu <guoguangwu@magic-shield.com>
Co-authored-by: Roshan Ganesh <73138775+CodingGod987@users.noreply.github.com>
Co-authored-by: Justin Grote <JustinGrote@users.noreply.github.com>
Co-authored-by: Ryan Yates <ryan.yates@kilasuit.org>
Co-authored-by: StepSecurity Bot <bot@stepsecurity.io>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
Co-authored-by: Steve Lee (POWERSHELL HE/HIM) (from Dev Box) <slee@ntdev.microsoft.com>
Co-authored-by: David Kontyko <33853225+dkontyko@users.noreply.github.com>
Co-authored-by: Tess Gauthier <tgauth@bu.edu>
Co-authored-by: Dave <reduckted@outlook.com>
chrisdent-de pushed a commit to chrisdent-de/PowerShell that referenced this pull request Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log CommunityDay-Small A small PR that the PS team has identified to prioritize to review Small WG-Interactive-Debugging debugging PowerShell script

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants