Skip to content

[Snyk] Upgrade cloudinary from 2.4.0 to 2.5.1 - #3

Open
leonardoGit99 wants to merge 1 commit into
mainfrom
snyk-upgrade-af08beb5b84b4c3048b169c09f7f9b93
Open

[Snyk] Upgrade cloudinary from 2.4.0 to 2.5.1#3
leonardoGit99 wants to merge 1 commit into
mainfrom
snyk-upgrade-af08beb5b84b4c3048b169c09f7f9b93

Conversation

@leonardoGit99

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade cloudinary from 2.4.0 to 2.5.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: cloudinary
  • 2.5.1 - 2024-10-08
    • fix: added missing stream method to ts spec
  • 2.5.0 - 2024-09-15
    • feat: auto_transcription on upload and explicit support (#690)
    • feat: auto_chaptering on upload and explicit support (#689)
    • feat: access key management via provisioning api (#687)
  • 2.4.0 - 2024-07-30
    • feat: exposing config endpoint from admin api
    • fix: update metadata field added missing param default_disabled
    • fix: types definitions
from cloudinary GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade cloudinary from 2.4.0 to 2.5.1.

See this package in npm:
cloudinary

See this project in Snyk:
https://app.snyk.io/org/login.davinci/project/f1a7e350-ae9f-401d-8517-68c5f76774c9?utm_source=github&utm_medium=referral&page=upgrade-pr
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.

2 participants