Skip to content

Conversation

@Hweinstock
Copy link
Contributor

@Hweinstock Hweinstock commented Nov 29, 2024

Problem

According to the comment in this file, there is an ignore pattern that is only needed on the vscode minimum version of 1.68, but we have bumped to 1.83.0.

Solution

Remove pattern for this case.


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Hweinstock Hweinstock marked this pull request as ready for review December 3, 2024 17:17
@Hweinstock Hweinstock requested a review from a team as a code owner December 3, 2024 17:17
Copy link
Contributor

@jpinkney-aws jpinkney-aws left a comment

Choose a reason for hiding this comment

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

I don't have context as to why that was ever needed but if it was happening on such a long release we should be good now

@justinmk3 justinmk3 changed the base branch from master to feature/postreinvent December 3, 2024 19:24
@justinmk3 justinmk3 changed the base branch from feature/postreinvent to master December 3, 2024 19:24
@justinmk3 justinmk3 merged commit 9a97f8a into aws:master Dec 3, 2024
36 of 54 checks passed
@justinmk3 justinmk3 changed the title build(pattern): remove ignore pattern related to 1.68 vscode version. ci(run_and_report): remove workaround for vscode 1.68 #6121 Dec 3, 2024
@justinmk3 justinmk3 changed the title ci(run_and_report): remove workaround for vscode 1.68 #6121 ci(run_and_report): remove workaround for vscode 1.68 Dec 3, 2024
@Hweinstock Hweinstock deleted the cleanUpIgnorePattern branch December 3, 2024 21:09
avi-alpert pushed a commit to avi-alpert/aws-toolkit-vscode that referenced this pull request Dec 4, 2024
## Problem
Ignore pattern that is only needed on the vscode minimum version of 1.68,
but we have bumped to 1.83.0.

## Solution
Remove pattern for this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants