doc(spec): deprecate the localisationReady key

[bfabio]

The boolean is basically a duplication of len(availableLanguages) > 1 and it could also describe a contradicting state, for example:

localisationReady: false
availableLanguages:
  - it
  - fr

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
publiccode-yml	Ready	Preview	Aug 26, 2026 1:52pm

[bfabio]

@yaml-9000 minor

[yaml-9000]

Thanks for your contribution 🙏

This is now marked as a minor-change proposal to the standard,
this means that old versions of publiccode.yml will still be valid with this change.

Example of minor changes are additions of new keys or making keys optional.

The next eligible voting round will take place on September 30, 2026

cc @publiccodeyml/steering-committee

_{📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands}

[dptdgi]

I do not see a real conflict.

A software with hard-coded translation that is translated in multiple languages, but does not use a proper infrastructure is possible.

There is also the case for partial translation.

An impact analysis will help to take an informed decision.

I prefer to keep localisationReady at this time.