chore: 🤖 resolve on-headers dependabot alert #3020
Open
+14
−14
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hashicc
approved these changes
Oct 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Resolves Dependabot Alert #192
The following dependencies were using on-headers. To resolve vulnerability, simply forced compression and morgan to resolve to newest possible version. As a result all
on-headersreferences should be on non-vulnerable version1.1.0.ember-cli -> compression -> on-headersember-cli -> morgan -> on-headersChecklist
[ ] I have added before and after screenshots for UI changes[ ] I have added JSON response output for API changes[ ] I have added steps to reproduce and test for bug fixes in the description[ ] I have commented on my code, particularly in hard-to-understand areas[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have addeda11y-testslabel to run a11y audit tests if neededPCI review checklist
[ ] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.[ ] If applicable, I've documented the impact of any changes to security controls.Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.