[DEV-2310] turbo upgrade

[tommaso1]

List of Changes

Upgrades turbo to the latest version to allow the upgrade of nextjs

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Chore (nothing changes by a user perspective)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[changeset-bot]

⚠️ No Changeset found

Latest commit: bf942c2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Jira Pull Request Link

This Pull Request refers to the following Jira issue DEV-2310

[github-actions]

Branch is not up to date with base branch

@marcobottaro it seems this Pull Request is not updated with base branch.
Please proceed with a merge or rebase to solve this.

[marcobottaro]

I think that this row was due because of the turbo prune command

[kin0992]

Turbo shouldn't be a workspace dependency, but in a mono repo, we use turbo to run some commands in any workspace.

so, the scripts of a single workspace (like the strapi-cms app) should not depend on turbo.
you could accomplish what you are doing now, making explicit the dependency between tasks (in the turbo.json file and updating (if necessary) your GitHub workflows.

If you do so, you will boost performance because you will also use the turbo cache (if the turbo.json file is properly configured).

[marcobottaro]

Why do we need to set an npm version here?

If this is necessary, I think you should also change .node-version file content and set 22.8.0 according to nodejs documentation: https://nodejs.org/dist/index.json

Does current Next and Strapi versions are compatible with npm 10.8.2?

[kin0992]

i left a note about the packageManager: it is a good practice to add it to the package.json file.
This adds consistency and makes sure the CI uses the same version used during development.

Moreover, I guess this has been introduced running the codemod to migrate turbo.

[github-actions]

This pull request is stale because it has been open for 14 days with no activity. If the pull request is still valid, please update it within 21 days to keep it open or merge it, otherwise it will be closed automatically.

[github-actions]

This pull request was closed because it has been inactive for 21 days since being marked as stale.