Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Feb 6, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Willem-J-an and others added 30 commits March 27, 2024 10:59
Removed the manual validation step because it is unnecesary (and annoying)
to gate this pipeline since it opens an unpublished, draft release.
The downstream triggered pipeline will gate the release to the VS Code
marketplace.
Instead of having to maintain an edited copy (which was really annoying)
I stubbed out `PSConsoleHostReadLine` to do what's expected.
So now we can just use the existing shell integration script directly!

Since we can't reliably find the script using
`code --locate-shell-integration-path pwsh` we now rely on it being sent
by the client on initialization. Its presence implies the feature is on.

This is pretty VS Code specific, but not necessarily so.

Apply suggestions from code review

Thanks Patrick!

Co-authored-by: Patrick Meinecke <[email protected]>
Bumps the xunit group with 1 update: [xunit](https://github.com/xunit/xunit).


Updates `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
  dependency-group: xunit
...

Signed-off-by: dependabot[bot] <[email protected]>
And so stop ignoring `VSTHRD002`.
By ensuring that our event queue is only accessed from the threadpool,
not the pipeline thread. We now do this in the event handler and the
assertions, instead of around calls to the `debugService`.
Avoiding pragmas wherever possible.
Which was silently broken due to a typo :(
The project is dormant an longer shipped/signed by Microsoft.
Until it's figured out how we're supposed to use these on GitHub.
It's having weird bugs and we're giving up on it.
Otherwise PR gates get stuck on documentation changes.
Fix bad file name for vim-simple-test.vim
And rely on GitHub's automatic action.
Differentiate Azure DevOps from GitHub Actions.
andyleejordan and others added 30 commits March 18, 2025 11:11
This info is in the readme.
Thanks dotnet-outdated.
* Initial plan

* Update PSReadLine to v2.4.2-beta2

Co-authored-by: andyleejordan <[email protected]>

* Address PR feedback: Move changelog entry to Unreleased section and add CFS feed reminder

Co-authored-by: andyleejordan <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: andyleejordan <[email protected]>
* Update getting_started.md with colorscheme troubleshooting step

* Update getting_started.md - Added troubleshooting for brackets after cmdlets when autocompleting

* Update getting_started.md - Added link to reference with more additional settings

---------

Co-authored-by: Andy Jordan <[email protected]>
* Support breakpoints in untitled files in WinPS

Adds support for setting breakpoints in untitled/unsaved files for
Windows PowerShell 5.1. This aligns the breakpoint validation behaviour
with the PowerShell 7.x API so that a breakpoint can be set for any
ScriptBlock with a filename if it aligns with the client's filename.

* Add fallback to Set-PSBreakpoint in case reflection can't find ctor

* Fix up wildcard handling

* Fix up command breakpoints for WinPS
* Add Start-DebugAttachSession function

Adds the `Start-DebugAttachSession` cmdlet which can be used to launch a
new attach session debug request inside an existing launched debug
session. This allows a script being debugged to launch a child debugging
session using more dynamic environment information without requiring end
users to manually setup the launch.json configuration.

* Apply suggestions from code review

Co-authored-by: Copilot <[email protected]>

* Remote mandatory param and update logic to exclude temp consoles

* Update module/PowerShellEditorServices/Commands/Public/Start-DebugAttachSession.ps1

* Add startDebugging tests

* Skip test in CLM

* Add test timeout and -AsJob test

---------

Co-authored-by: Copilot <[email protected]>
Adds the parameter `-WindowActionOnEnd` that corresponds to the new
VSCode attach configuration option
`temporaryConsoleWindowActionOnDebugEnd`.
* Add missing MEL log levels to the LogLevel parameter in Start-EditorServices.ps1 (#2235)

This commit adds `Trace`, `Debug`, `Information`, `Critical`, and `None`
to the validation set on the `LogLevel` parameter when starting PSES
using `Start-EditorServices.ps1` to allow for the adoption of the newer
MEL log levels.

* Add legacy log level translations

---------

Co-authored-by: Justin Grote <[email protected]>
Adds the `pathMappings` option to the debugger that can be used to map a
local to remote path and vice versa. This is useful if the local
environment has a checkout of the files being run on a remote target but
at a different path. The mappings are used to translate the paths that
will the breakpoint will be set to in the target PowerShell instance. It
is also used to update the stack trace paths received from the remote.
It was being used for tests but that has already stopped.
With NonOfficial available for testing.
Since it's shared.
Since we're reusing this YAML for the NonOfficial and Official pipelines,
we can't use a YAML cron job for just one of them.
Hence we'll schedule this job in the UI.
Since there is no way to do this in the UI,
but we also went down to one pipeline.
The weekly CodeQL task requires being run as an official build,
hence CodeQL was not yet running.
The easiest fix is to set the parameter controlling that to default to true,
which means introducing another parameter controlling whether to release
(which defaults to false).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.