v1.0.0

[PeteBishwhip]

🎉 Laradocs v1.0.0 — we're stable!

This is the big one. After the whole 0.x journey, Laradocs is officially 1.0.0 stable, with a frozen public API, a full migration path, and the feature we've been building towards for months: a native OpenAPI renderer.

Thank you to everyone who kicked the tyres through the pre-releases. Let's ship. 🚀

✨ Highlights

📖 Native OpenAPI renderer

The headline of this release. Laradocs now renders OpenAPI specs natively, no external doc UI required.

• Pillars A & B land the core rendering engine (feat: OpenAPI native renderer (Pillars A & B) #140)
• A redesigned reference layout with a request/response code-sample sidebar (feat: redesign OpenAPI reference + request/response code-sample sidebar #143)
• Driver selection: pick native, Scramble, or auto and let Laradocs decide (feat: OpenAPI generator driver selection (native / Scramble / auto) #147)
• Clean, summary-based operation slugs so your URLs read like docs, not hashes (docs + feat: OpenAPI guide, plus clean summary-based operation slugs #144)
• A dedicated OpenAPI guide plus updated system requirements (docs + feat: OpenAPI guide, plus clean summary-based operation slugs #144, docs: add OpenAPI package requirements to system requirements #141)

🗂️ Tabbed code blocks and content tabs

Group your bash / php / json samples into tabs, and organise longer pages with content tabs (#138).

🌍 Internationalisation

• "Last updated" dates now localise to the active docs locale (feat: localize "Last updated" date using the active docs locale #139)
• Cookie consent integration so a reader's chosen language persists properly (i18n: cookie consent integration for language persistence #150)

🔒 Stability and security

• The public PHP API surface is now frozen (Freeze the public PHP API surface #149). From here, semver means what it says.
• Security hardening around exec usage to close a potential RCE path ([Aikido] AI Fix for Unsafe exec usage can lead to remote code execution #154)
• A new production readiness checklist (docs: add production readiness checklist #151)
• A full 0.x to 1.0 migration guide (Add migration guide: 0.x → 1.0 #152)

⬆️ Upgrading from 0.x

Please read the migration guide in #152 before bumping. There are a small number of breaking changes tied to the API freeze, and the guide walks through each one.

What's Changed

• feat: tabbed code blocks and content tabs by @PeteBishwhip in feat: tabbed code blocks and content tabs #138
• feat: localize "Last updated" date using the active docs locale by @PeteBishwhip in feat: localize "Last updated" date using the active docs locale #139
• feat: OpenAPI native renderer (Pillars A & B) by @PeteBishwhip in feat: OpenAPI native renderer (Pillars A & B) #140
• docs: add OpenAPI package requirements to system requirements by @PeteBishwhip in docs: add OpenAPI package requirements to system requirements #141
• feat: redesign OpenAPI reference + request/response code-sample sidebar by @PeteBishwhip in feat: redesign OpenAPI reference + request/response code-sample sidebar #143
• docs + feat: OpenAPI guide, plus clean summary-based operation slugs by @PeteBishwhip in docs + feat: OpenAPI guide, plus clean summary-based operation slugs #144
• feat: OpenAPI generator driver selection (native / Scramble / auto) by @PeteBishwhip in feat: OpenAPI generator driver selection (native / Scramble / auto) #147
• New Crowdin updates by @PeteBishwhip in New Crowdin updates #146
• Freeze the public PHP API surface by @PeteBishwhip in Freeze the public PHP API surface #149
• i18n: cookie consent integration for language persistence by @PeteBishwhip in i18n: cookie consent integration for language persistence #150
• docs: add production readiness checklist by @PeteBishwhip in docs: add production readiness checklist #151
• Add migration guide: 0.x → 1.0 by @PeteBishwhip in Add migration guide: 0.x → 1.0 #152
• docs: v1.0 release prep (changelog, README badges) by @PeteBishwhip in docs: v1.0 release prep (changelog, README badges) #153
• [Aikido] AI Fix for Unsafe exec usage can lead to remote code execution by @aikido-autofix[bot] in [Aikido] AI Fix for Unsafe exec usage can lead to remote code execution #154

New Contributors

• @aikido-autofix[bot] made their first contribution in [Aikido] AI Fix for Unsafe exec usage can lead to remote code execution #154

Full Changelog: v0.6.1...v1.0.0

---

This discussion was created from the release v1.0.0.