Bump the npm_and_yarn group across 1 directory with 2 updates #304
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the npm_and_yarn group with 2 updates in the /sandboxes/IntercomExpo directory: [on-headers](https://github.com/jshttp/on-headers) and [compression](https://github.com/expressjs/compression). Updates `on-headers` from 1.0.2 to 1.1.0 - [Release notes](https://github.com/jshttp/on-headers/releases) - [Changelog](https://github.com/jshttp/on-headers/blob/master/HISTORY.md) - [Commits](jshttp/on-headers@v1.0.2...v1.1.0) Updates `compression` from 1.8.0 to 1.8.1 - [Release notes](https://github.com/expressjs/compression/releases) - [Changelog](https://github.com/expressjs/compression/blob/master/HISTORY.md) - [Commits](expressjs/compression@1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: on-headers dependency-version: 1.1.0 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: compression dependency-version: 1.8.1 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
It looks like you are reviewing a Dependabot upgrade PR! 🛠️ We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:
🎯 Target merge date for this PR: 16/10/2025 🎯 FAQ What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package?It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.What if we’re not vulnerable and upgrading is going to be a lot of work?In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing anyCRITICAL alerts.
This is a major version upgrade that requires substantial code refactoring. What should I do?If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add thedependabot-refactor-required label to this PR and ping #ask-security for further advice.
|
|
|
|
|
5 similar comments
|
|
|
|
|
|
|
|
|
|
Bumps the npm_and_yarn group with 2 updates in the /sandboxes/IntercomExpo directory: on-headers and compression.
Updates
on-headersfrom 1.0.2 to 1.1.0Release notes
Sourced from on-headers's releases.
Changelog
Sourced from on-headers's changelog.
Commits
4b017af1.1.0b636f2d♻️ refactor header array code3e2c2d4✨ ignore falsy header keys, matching node behavior172eb41✨ support duplicate headersc6e3849🔒️ fix array handling6893518💚 update CI - add newer node versions56a345d✨ add script to update known hashes175ab21👷 add upstream change detection (#31)ce0b2c8ci: apply OSSF Scorecard security best practices (#20)1a38c54fix: useubuntu-latestas ci runner (#19)Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for on-headers since your current version.
Updates
compressionfrom 1.8.0 to 1.8.1Release notes
Sourced from compression's releases.
Changelog
Sourced from compression's changelog.
Commits
83a0c451.8.1ce62713deps: [email protected] (#246)f4acb23build(deps-dev): bump eslint-plugin-import from 2.31.0 to 2.32.0 (#244)6eaebe6build(deps): bump actions/checkout from 4.1.1 to 4.2.2 (#241)37e0623build(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 (#240)bc436b2build(deps): bump actions/upload-artifact from 4.3.1 to 4.6.2 (#239)2f9f572build(deps): bump github/codeql-action from 3.28.15 to 3.29.2 (#243)5f13b14[StepSecurity] ci: Harden GitHub Actions (#235)76e0945build(deps-dev): bump supertest from 6.2.3 to 6.3.4 (#231)ae6ee80build(deps-dev): bump eslint-plugin-import from 2.26.0 to 2.31.0 (#230)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.