131 create automation for strapi version update

[matej-marcisovsky]

Task Link

#131

Description

Dependabot now opens one monthly pull request against main for @strapi/* patch and minor updates across the monorepo.

@strapi/strapi in apps/strapi and packages/strapi-types now uses catalog:, so that version lives in pnpm-workspace.yaml and Dependabot can update it there.

Checklist - author

• Assignee is set (the active developer of this PR).
• Reviewers are set (team members who will review the code).
• PR is linked I have linked the PR to an issue in Jira.
• Description I have described the changes proposed in the PR clearly and concisely (more important than what is why).
• Screenshots/Videos I have added screenshots/videos or they were not needed.
• Environmental variables are listed or they were not needed.
• Unit/Integration tests are added for all utilities and business important logic
• Labels I have added labels to the PR.
  • Use requires-env-vars when PR requires environmental variables
  • Use ready-for-review when PR is ready to be looked at
  • Use ready-to-merge when PR has a passing review
  • Use needs-revisions when PR has comments that block merge
  • Use do-not-review when PR is daft only and you don't want to get a review
• [OPTIONAL] Conversation/documentation is started in places where the code is not self-explanatory

Before merging

• PR is approved
• All conversations are resolved
• Pipelines are not failing

Checklist - reviewer

• I understand all proposed changes.
• Necessary after deploy steps are handled by someone (adding new env var, syncing config, running migration...)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
website-ui	Ready	Preview	Oct 5, 2026 8:54am UTC

[fonodi]

Nice, thank you 👍