Fix test expectations after action pins update and safe outputs refactoring #7817
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.
Two test suites were failing due to outdated expectations after recent changes.
Changes
Go test: Updated
TestGetActionPinsSortingto expect 29 action pins (was 27)action_pins.jsonnow contains 29 entries after recent additionsJavaScript tests: Fixed
log_parser_bootstrap.test.cjsexpectations after safe outputs refactoring## 📤 Safe Outputsto collapsible<details><summary>Safe Outputs</summary>warning()is called when file doesn't exist (code only warns on read errors, not missing files)The failing tests were checking for old behavior that was legitimately changed by recent commits.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.