Skip to content

Conversation

@agungjati
Copy link
Contributor

@agungjati agungjati commented Oct 31, 2024

Related #6103 (comment)

@UlisesGascon UlisesGascon changed the title upgrade content type deps: upgrade content-type Nov 1, 2024
@UlisesGascon UlisesGascon self-assigned this Nov 1, 2024
Copy link
Member

@wesleytodd wesleytodd left a comment

Choose a reason for hiding this comment

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

When we are upgrading deps we are using the ^ range specifier.

wesleytodd pushed a commit that referenced this pull request Feb 13, 2025
fix(deps): mocha@^10.7.3 (closes #6121)

fix(deps): marked@^15.0.3 (closes #6120)

fix(deps): express-session@^1.18.1 (closes #6119)

fix(deps): ejs@^3.1.10 (closes #6117)

fix(deps): content-type@^1.0.5 (closes #6115)

fix(deps): connect-redis@^8.0.1 (closes #6114)

fix(deps): supertest@^7.0.0 (closes #6112)
wesleytodd pushed a commit that referenced this pull request Feb 13, 2025
fix(deps): mocha@^10.7.3 (closes #6121)

fix(deps): marked@^15.0.3 (closes #6120)

fix(deps): express-session@^1.18.1 (closes #6119)

fix(deps): ejs@^3.1.10 (closes #6117)

fix(deps): content-type@^1.0.5 (closes #6115)

fix(deps): connect-redis@^8.0.1 (closes #6114)

fix(deps): supertest@^6.3.4 (closes #6112)
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