Skip to content

Comments

Bump @strapi/utils, @strapi/strapi, @strapi/plugin-graphql, @strapi/plugin-i18n and @strapi/plugin-users-permissions#7

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/strapi/utils-and-strapi/strapi-and-strapi/plugin-graphql-and-strapi/plugin-i18n-and-strapi/plugin-users-permissions-4.13.1
Closed

Bump @strapi/utils, @strapi/strapi, @strapi/plugin-graphql, @strapi/plugin-i18n and @strapi/plugin-users-permissions#7
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/strapi/utils-and-strapi/strapi-and-strapi/plugin-graphql-and-strapi/plugin-i18n-and-strapi/plugin-users-permissions-4.13.1

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Aug 30, 2023

Bumps @strapi/utils to 4.13.1 and updates ancestor dependencies @strapi/utils, @strapi/strapi, @strapi/plugin-graphql, @strapi/plugin-i18n and @strapi/plugin-users-permissions. These dependencies need to be updated together.

Updates @strapi/utils from 4.9.0 to 4.13.1

Release notes

Sourced from @​strapi/utils's releases.

v4.13.1

⚠️ Breaking Changes ⚠️

Starting with Strapi v4.13.1, requests to the Content API using invalid query parameters will be rejected with an error response instead of being silently removed from the query. If you are seeing “Invalid parameter” errors in a Content API request, please ensure that every parameter in your query string is valid. If you need the previous behavior of filtering out invalid parameters, you will need to use a custom controller that only calls sanitizeQuery and not validateQuery. For more information as to why we made this change please see #17001

⚠️ Security Warning and Notice ⚠️

Strapi was made aware of a few vulnerabilities that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.

For now the delay timeline looks like we will release the detailed information in the next two (2) weeks, we expect to do public disclosure (via a blog post) on Wednesday Sept 13th, 2023. The previous disclosure mentioned in v4.12.1 was delayed and will also be disclosed on Speth 13th, 2023.

💅 Enhancement

🚀 New feature

🔥 Bug fix

🚨 Security

⚙️ Chore

📚 Update and Migration Guides

... (truncated)

Commits
  • a9afeb9 v4.13.1
  • 2cb056a Merge pull request #17862 from strapi/fix/dont-clean-creator-fields
  • d3eda9f add test cases
  • e595b11 Merge pull request #17865 from strapi/fix/disable-rw-on-user
  • 066c1ba chore: remove space
  • d7f1a83 fix: add review workflow types in the ignoreDiffs list
  • a720271 fix: ignore review workflow fields in users and permissions user
  • 329de13 Revert "fix: remove review workflows from users and permissions"
  • f0d5be0 fix: remove review workflows from users and permissions
  • 2b71831 move creator fields to a constant
  • Additional commits viewable in compare view

Updates @strapi/strapi from 4.9.0 to 4.13.1

Release notes

Sourced from @​strapi/strapi's releases.

v4.13.1

⚠️ Breaking Changes ⚠️

Starting with Strapi v4.13.1, requests to the Content API using invalid query parameters will be rejected with an error response instead of being silently removed from the query. If you are seeing “Invalid parameter” errors in a Content API request, please ensure that every parameter in your query string is valid. If you need the previous behavior of filtering out invalid parameters, you will need to use a custom controller that only calls sanitizeQuery and not validateQuery. For more information as to why we made this change please see #17001

⚠️ Security Warning and Notice ⚠️

Strapi was made aware of a few vulnerabilities that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.

For now the delay timeline looks like we will release the detailed information in the next two (2) weeks, we expect to do public disclosure (via a blog post) on Wednesday Sept 13th, 2023. The previous disclosure mentioned in v4.12.1 was delayed and will also be disclosed on Speth 13th, 2023.

💅 Enhancement

🚀 New feature

🔥 Bug fix

🚨 Security

⚙️ Chore

📚 Update and Migration Guides

... (truncated)

Commits
  • a9afeb9 v4.13.1
  • 2cb056a Merge pull request #17862 from strapi/fix/dont-clean-creator-fields
  • d3eda9f add test cases
  • e595b11 Merge pull request #17865 from strapi/fix/disable-rw-on-user
  • 066c1ba chore: remove space
  • d7f1a83 fix: add review workflow types in the ignoreDiffs list
  • a720271 fix: ignore review workflow fields in users and permissions user
  • 329de13 Revert "fix: remove review workflows from users and permissions"
  • f0d5be0 fix: remove review workflows from users and permissions
  • 2b71831 move creator fields to a constant
  • Additional commits viewable in compare view

Updates @strapi/plugin-graphql from 4.9.0 to 4.13.1

Release notes

Sourced from @​strapi/plugin-graphql's releases.

v4.13.1

⚠️ Breaking Changes ⚠️

Starting with Strapi v4.13.1, requests to the Content API using invalid query parameters will be rejected with an error response instead of being silently removed from the query. If you are seeing “Invalid parameter” errors in a Content API request, please ensure that every parameter in your query string is valid. If you need the previous behavior of filtering out invalid parameters, you will need to use a custom controller that only calls sanitizeQuery and not validateQuery. For more information as to why we made this change please see #17001

⚠️ Security Warning and Notice ⚠️

Strapi was made aware of a few vulnerabilities that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.

For now the delay timeline looks like we will release the detailed information in the next two (2) weeks, we expect to do public disclosure (via a blog post) on Wednesday Sept 13th, 2023. The previous disclosure mentioned in v4.12.1 was delayed and will also be disclosed on Speth 13th, 2023.

💅 Enhancement

🚀 New feature

🔥 Bug fix

🚨 Security

⚙️ Chore

📚 Update and Migration Guides

... (truncated)

Commits
  • a9afeb9 v4.13.1
  • a2b1a1e Merge branch 'temp-fix'
  • fefc4a2 v4.12.7
  • 8ceaa69 Add comment about gql single type resolve validation
  • 8c212ec Merge branch 'fix/sanitization-throw-instead-of-filter' of github.com:strapi/...
  • aedf994 Merge branch 'main' into fix/sanitization-throw-instead-of-filter
  • 4e6503d Add comments to the single type graphql mutations
  • 9bb6ba1 v4.12.6
  • f7022c5 fix single type sanitization
  • 9ebce88 Merge branch 'main' into fix/sanitization-throw-instead-of-filter
  • Additional commits viewable in compare view

Updates @strapi/plugin-i18n from 4.9.0 to 4.13.1

Release notes

Sourced from @​strapi/plugin-i18n's releases.

v4.13.1

⚠️ Breaking Changes ⚠️

Starting with Strapi v4.13.1, requests to the Content API using invalid query parameters will be rejected with an error response instead of being silently removed from the query. If you are seeing “Invalid parameter” errors in a Content API request, please ensure that every parameter in your query string is valid. If you need the previous behavior of filtering out invalid parameters, you will need to use a custom controller that only calls sanitizeQuery and not validateQuery. For more information as to why we made this change please see #17001

⚠️ Security Warning and Notice ⚠️

Strapi was made aware of a few vulnerabilities that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.

For now the delay timeline looks like we will release the detailed information in the next two (2) weeks, we expect to do public disclosure (via a blog post) on Wednesday Sept 13th, 2023. The previous disclosure mentioned in v4.12.1 was delayed and will also be disclosed on Speth 13th, 2023.

💅 Enhancement

🚀 New feature

🔥 Bug fix

🚨 Security

⚙️ Chore

📚 Update and Migration Guides

... (truncated)

Commits
  • a9afeb9 v4.13.1
  • 6f1d9a1 Revert "Fix: Use sync over async components in admin panel APIs"
  • a2b1a1e Merge branch 'temp-fix'
  • fefc4a2 v4.12.7
  • 60f5155 Merge branch 'main' into releases/4.12.6
  • 9bb6ba1 v4.12.6
  • 4b69d56 Fix: Use React.lazy over async component imports for plugins
  • 83f7cdd Merge branch 'main' into releases/4.12.5
  • c1935e7 v4.12.5
  • cfa980b Chore: Add support for valencian locale
  • Additional commits viewable in compare view

Updates @strapi/plugin-users-permissions from 4.9.0 to 4.13.1

Release notes

Sourced from @​strapi/plugin-users-permissions's releases.

v4.13.1

⚠️ Breaking Changes ⚠️

Starting with Strapi v4.13.1, requests to the Content API using invalid query parameters will be rejected with an error response instead of being silently removed from the query. If you are seeing “Invalid parameter” errors in a Content API request, please ensure that every parameter in your query string is valid. If you need the previous behavior of filtering out invalid parameters, you will need to use a custom controller that only calls sanitizeQuery and not validateQuery. For more information as to why we made this change please see #17001

⚠️ Security Warning and Notice ⚠️

Strapi was made aware of a few vulnerabilities that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.

For now the delay timeline looks like we will release the detailed information in the next two (2) weeks, we expect to do public disclosure (via a blog post) on Wednesday Sept 13th, 2023. The previous disclosure mentioned in v4.12.1 was delayed and will also be disclosed on Speth 13th, 2023.

💅 Enhancement

🚀 New feature

🔥 Bug fix

🚨 Security

⚙️ Chore

📚 Update and Migration Guides

... (truncated)

Commits
  • a9afeb9 v4.13.1
  • 2cb056a Merge pull request #17862 from strapi/fix/dont-clean-creator-fields
  • d3eda9f add test cases
  • e595b11 Merge pull request #17865 from strapi/fix/disable-rw-on-user
  • 066c1ba chore: remove space
  • d7f1a83 fix: add review workflow types in the ignoreDiffs list
  • a720271 fix: ignore review workflow fields in users and permissions user
  • 329de13 Revert "fix: remove review workflows from users and permissions"
  • f0d5be0 fix: remove review workflows from users and permissions
  • 2b71831 move creator fields to a constant
  • Additional commits viewable in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump @strapi/utils, @strapi/strapi, @strapi/plugin-graphql, @strapi/p…
b527c4f 
…lugin-i18n and @strapi/plugin-users-permissions

Bumps [@strapi/utils](https://github.com/strapi/strapi) to 4.13.1 and updates ancestor dependencies [@strapi/utils](https://github.com/strapi/strapi), [@strapi/strapi](https://github.com/strapi/strapi), [@strapi/plugin-graphql](https://github.com/strapi/strapi/tree/HEAD/packages/plugins/graphql), [@strapi/plugin-i18n](https://github.com/strapi/strapi/tree/HEAD/packages/plugins/i18n) and [@strapi/plugin-users-permissions](https://github.com/strapi/strapi). These dependencies need to be updated together.


Updates `@strapi/utils` from 4.9.0 to 4.13.1
- [Release notes](https://github.com/strapi/strapi/releases)
- [Commits](strapi/strapi@v4.9.0...v4.13.1)

Updates `@strapi/strapi` from 4.9.0 to 4.13.1
- [Release notes](https://github.com/strapi/strapi/releases)
- [Commits](strapi/strapi@v4.9.0...v4.13.1)

Updates `@strapi/plugin-graphql` from 4.9.0 to 4.13.1
- [Release notes](https://github.com/strapi/strapi/releases)
- [Commits](https://github.com/strapi/strapi/commits/v4.13.1/packages/plugins/graphql)

Updates `@strapi/plugin-i18n` from 4.9.0 to 4.13.1
- [Release notes](https://github.com/strapi/strapi/releases)
- [Commits](https://github.com/strapi/strapi/commits/v4.13.1/packages/plugins/i18n)

Updates `@strapi/plugin-users-permissions` from 4.9.0 to 4.13.1
- [Release notes](https://github.com/strapi/strapi/releases)
- [Commits](strapi/strapi@v4.9.0...v4.13.1)

---
updated-dependencies:
- dependency-name: "@strapi/utils"
  dependency-type: indirect
- dependency-name: "@strapi/strapi"
  dependency-type: direct:production
- dependency-name: "@strapi/plugin-graphql"
  dependency-type: direct:production
- dependency-name: "@strapi/plugin-i18n"
  dependency-type: direct:production
- dependency-name: "@strapi/plugin-users-permissions"
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 30, 2023
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 13, 2023

Superseded by #11.

@dependabot dependabot bot closed this Sep 13, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/strapi/utils-and-strapi/strapi-and-strapi/plugin-graphql-and-strapi/plugin-i18n-and-strapi/plugin-users-permissions-4.13.1 branch September 13, 2023 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants