chore: auto-upgrade demo strapi

[nclsndr]

What does it do?

• Upgrading demo/.strapi-app strapi version to 5.31.0
• Add a GitHub action to update the version over a PR every Wed night (after Strapi weekly release)

Why is it needed?

• Making sure any work done testing on client uses the latest Strapi.

How to test it?

Launch demo app: cd demo/.strapi-app && pnpm i && pnpm develop

Related issue(s)/PR(s)

[Convly]

What was the issue with using latest here?

[nclsndr]

What was the issue with using latest here?

@Convly - The exact version is still pinned into the pnpm lock file, hiding the actual installed version from our eyes (since the lock file is long, GH previews are usually disabled by default).
I feel it's simpler to keep track with the version declared in package.json, with the automation attached, it would make the maintenance trivial.

[innerdvations]

going off @Convly 's comment, how about we keep it latest but have the script run pnpm up periodically?

[nclsndr]

With exact version being listed in package.json, it allows the action to use it as state and derive the comparison from it.
If we go back to latest, we'd have to either:

• pnpm install then pnpm up ...@latest then, look into the node_modules/@strapi/strapi/package.json to observe a diff, then conditionally make the PR.
• Rely on reading the lock file with a regex to match the @strapi/strapi version declaration, which I find clunky

@Convly @innerdvations can you detail the rationale/preference behind keeping latest instead of a pinned version?

[Bassel17]

I have no strong opinion here, but I think I have to agree with Nico here regarding pinned versions in package.json
Having explicit versions in the diff makes it much easier to see what actually changed. It’s valuable for debugging and for understanding compatibility issues across both sides.

That said, I’d also suggest running the update job more frequently than once a week on Wednesday. We sometimes release on Thursdays, and we occasionally ship hotfixes as well. A more frequent schedule (e.g. daily ) would keep the example app synced much more reliably and reduce the lag between Strapi releases and the example’s updates.