fix: better handling of whitespace (backport to v5) - #585
Merged
Conversation
joaomoreno
force-pushed
the
joao/backport-564-to-v5
branch
from
July 7, 2023 13:47
0572517 to
57bfd39
Compare
Contributor
|
#580 should be fixed before we go backporting anything so we don't bring new bugs along. |
Contributor
|
#587 Also needs to be fixed |
lukekarrys
force-pushed
the
release/v5
branch
2 times, most recently
from
July 7, 2023 17:50
b67c2f8 to
deb5ad5
Compare
Contributor
|
the latest template-oss changes have been applied to |
Contributor
lukekarrys
force-pushed
the
joao/backport-564-to-v5
branch
from
July 7, 2023 22:37
74351cf to
d4530b8
Compare
Contributor
|
@joaomoreno i was able to push to your branch with the relevant commits. waiting on CI to see if tests pass in older versions of node |
1 task
Author
|
Sounds good, thanks @lukekarrys! |
wraithgar
approved these changes
Jul 10, 2023
Merged
|
I've opened github/advisory-database#2483 updating the advisory for v5 |
|
and I've opened github/advisory-database#2484 updating the advisory again for v6 and v5. |
Contributor
|
Thanks @G-Rath! |
Author
|
Thanks all! |
This was referenced Sep 24, 2024
This was referenced Oct 2, 2024
This was referenced Nov 6, 2024
This was referenced Jan 28, 2025
This was referenced Feb 10, 2025
Open
This was referenced Apr 25, 2025
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
This backports the security fix #564 to v5.