[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-php-82-security-support-ends-december-2026":3,"blog-nav-php-82-security-support-ends-december-2026":27},{"slug":4,"title":5,"description":6,"body":7,"category":8,"readTime":9,"tags":10,"coverImage":14,"coverImageAlt":15,"heroImage":16,"heroImageAlt":15,"metaTitle":17,"metaDescription":18,"ogImage":19,"noindex":20,"published":21,"publishAt":22,"sortOrder":23,"updatedAt":22,"status":24,"path":25,"bodyHtml":26},"php-82-security-support-ends-december-2026","PHP 8.2 security support ends on 31 December 2026","PHP 8.2 security fixes stop on 31 December 2026. You can move the runtime and stay on Laravel 12. The framework calendar is a different decision.","PHP 8.2 stops receiving security fixes on **31 December 2026**. That calendar is not the Laravel 13 upgrade question. Teams keep folding them together, then either freeze both or bump both in one weekend.\n\nThis is the runtime decision. The framework decision already has its own article.\n\n## What ends in December\n\nThe PHP project publishes the dates on [supported versions](https:\u002F\u002Fwww.php.net\u002Fsupported-versions.php\u002F). Active support is bug fixes. After that, a branch gets security fixes only, and then nothing.\n\n| Branch | Active support | Security fixes until |\n|--------|----------------|----------------------|\n| 8.2 | Ended 31 Dec 2024 | **31 Dec 2026** |\n| 8.3 | Ended 31 Dec 2025 | 31 Dec 2027 |\n| 8.4 | Until 31 Dec 2026 | 31 Dec 2028 |\n| 8.5 | Until 31 Dec 2027 | 31 Dec 2029 |\n\nAfter 31 December 2026, PHP 8.2 is not “a bit behind.” The PHP project will not patch it. A Laravel security release does not fill that hole.\n\n## This is not the Laravel 13 decision\n\n[Should Philippine teams upgrade to Laravel 13](\u002Fblog\u002Fshould-philippine-teams-upgrade-to-laravel-13) is about the framework major. Laravel 12 still receives security fixes until **24 February 2027**, and it runs on PHP 8.2 through 8.5. Laravel 13 requires **PHP 8.3 or newer**. Those facts are on the [Laravel 13 release notes](https:\u002F\u002Flaravel.com\u002Fdocs\u002F13.x\u002Freleases).\n\nYou can move the runtime and stay on Laravel 12. You should not stay on PHP 8.2 past December and call the app supported because the framework line has not ended.\n\nPHP 8.3 is already in security-only support, through 2027. PHP 8.4 is in active support until the end of 2026, then security fixes through 2028. PHP 8.5 is current if the host and extensions are ready. “Newest” is not the requirement. **Still receiving fixes after December** is.\n\n## What we change first\n\n1. Read `php -v` on the web box, the queue workers, and CI. They drift apart more often than the `composer.json` platform line admits.\n2. Move staging to 8.3 or 8.4 and re-run the paths that take money, create bookings, or send mail. Extension and signature changes show up there, not in a homepage refresh.\n3. Ship the runtime by itself. Do not combine it with a Laravel major and a new feature.\n4. Decide the framework upgrade after production has been on the new PHP long enough to trust it. The sequence in the Laravel 13 article is the same: **runtime first**.\n\nWhere the process actually runs is a hosting question. [Philippine data centers vs APAC cloud](\u002Fblog\u002Fphilippine-data-centers-where-to-host-nuxt-laravel) is that choice. A region does not pick your PHP version. The image you deploy does.\n\n## What we will not pretend\n\n- Framework support is not language support.\n- A shared host that cannot leave 8.2 is a hosting constraint, not a reason to skip the date.\n- “We will get to it in January” means you plan to run an unpatched language. Write the date or move the date up.\n\n## Straight next step\n\nIf you have a production Laravel app and you are not sure which PHP is actually running, [send the version from the server and the workers](\u002Fcontact). We will say whether December is a runtime change only, or whether the framework major has to travel with it.","Trends",7,[11,12,13],"PHP","Laravel","Upgrades","\u002Fimages\u002Fjournal\u002Fphp-82-security-support-ends-december-2026-cover.webp?v=20261013b","Source code on a computer monitor","\u002Fimages\u002Fjournal\u002Fphp-82-security-support-ends-december-2026-hero.webp?v=20261013b","PHP 8.2 Security Support Ends 31 Dec 2026 | PrimeCode","PHP 8.2 security fixes stop on 31 December 2026. What that means if you stay on Laravel 12, and when PHP 8.3 or 8.4 is the move.","\u002Fimages\u002Fjournal\u002Fphp-82-security-support-ends-december-2026-og.webp?v=20261013b",false,true,"2026-10-02T01:00:00.000Z",46,"live","\u002Fblog\u002Fphp-82-security-support-ends-december-2026","\u003Cp>PHP 8.2 stops receiving security fixes on \u003Cstrong>31 December 2026\u003C\u002Fstrong>. That calendar is not the Laravel 13 upgrade question. Teams keep folding them together, then either freeze both or bump both in one weekend.\u003C\u002Fp>\n\u003Cp>This is the runtime decision. The framework decision already has its own article.\u003C\u002Fp>\n\u003Ch2>What ends in December\u003C\u002Fh2>\n\u003Cp>The PHP project publishes the dates on \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fsupported-versions.php\u002F\" rel=\"noopener noreferrer\">supported versions\u003C\u002Fa>. Active support is bug fixes. After that, a branch gets security fixes only, and then nothing.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Branch\u003C\u002Fth>\n\u003Cth>Active support\u003C\u002Fth>\n\u003Cth>Security fixes until\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>8.2\u003C\u002Ftd>\n\u003Ctd>Ended 31 Dec 2024\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>31 Dec 2026\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>8.3\u003C\u002Ftd>\n\u003Ctd>Ended 31 Dec 2025\u003C\u002Ftd>\n\u003Ctd>31 Dec 2027\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>8.4\u003C\u002Ftd>\n\u003Ctd>Until 31 Dec 2026\u003C\u002Ftd>\n\u003Ctd>31 Dec 2028\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>8.5\u003C\u002Ftd>\n\u003Ctd>Until 31 Dec 2027\u003C\u002Ftd>\n\u003Ctd>31 Dec 2029\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>After 31 December 2026, PHP 8.2 is not “a bit behind.” The PHP project will not patch it. A Laravel security release does not fill that hole.\u003C\u002Fp>\n\u003Ch2>This is not the Laravel 13 decision\u003C\u002Fh2>\n\u003Cp>\u003Ca href=\"\u002Fblog\u002Fshould-philippine-teams-upgrade-to-laravel-13\" rel=\"noopener noreferrer\">Should Philippine teams upgrade to Laravel 13\u003C\u002Fa> is about the framework major. Laravel 12 still receives security fixes until \u003Cstrong>24 February 2027\u003C\u002Fstrong>, and it runs on PHP 8.2 through 8.5. Laravel 13 requires \u003Cstrong>PHP 8.3 or newer\u003C\u002Fstrong>. Those facts are on the \u003Ca href=\"https:\u002F\u002Flaravel.com\u002Fdocs\u002F13.x\u002Freleases\" rel=\"noopener noreferrer\">Laravel 13 release notes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>You can move the runtime and stay on Laravel 12. You should not stay on PHP 8.2 past December and call the app supported because the framework line has not ended.\u003C\u002Fp>\n\u003Cp>PHP 8.3 is already in security-only support, through 2027. PHP 8.4 is in active support until the end of 2026, then security fixes through 2028. PHP 8.5 is current if the host and extensions are ready. “Newest” is not the requirement. \u003Cstrong>Still receiving fixes after December\u003C\u002Fstrong> is.\u003C\u002Fp>\n\u003Ch2>What we change first\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Read \u003Ccode>php -v\u003C\u002Fcode> on the web box, the queue workers, and CI. They drift apart more often than the \u003Ccode>composer.json\u003C\u002Fcode> platform line admits.\u003C\u002Fli>\n\u003Cli>Move staging to 8.3 or 8.4 and re-run the paths that take money, create bookings, or send mail. Extension and signature changes show up there, not in a homepage refresh.\u003C\u002Fli>\n\u003Cli>Ship the runtime by itself. Do not combine it with a Laravel major and a new feature.\u003C\u002Fli>\n\u003Cli>Decide the framework upgrade after production has been on the new PHP long enough to trust it. The sequence in the Laravel 13 article is the same: \u003Cstrong>runtime first\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Where the process actually runs is a hosting question. \u003Ca href=\"\u002Fblog\u002Fphilippine-data-centers-where-to-host-nuxt-laravel\" rel=\"noopener noreferrer\">Philippine data centers vs APAC cloud\u003C\u002Fa> is that choice. A region does not pick your PHP version. The image you deploy does.\u003C\u002Fp>\n\u003Ch2>What we will not pretend\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Framework support is not language support.\u003C\u002Fli>\n\u003Cli>A shared host that cannot leave 8.2 is a hosting constraint, not a reason to skip the date.\u003C\u002Fli>\n\u003Cli>“We will get to it in January” means you plan to run an unpatched language. Write the date or move the date up.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Straight next step\u003C\u002Fh2>\n\u003Cp>If you have a production Laravel app and you are not sure which PHP is actually running, \u003Ca href=\"\u002Fcontact\" rel=\"noopener noreferrer\">send the version from the server and the workers\u003C\u002Fa>. We will say whether December is a runtime change only, or whether the framework major has to travel with it.\u003C\u002Fp>\n",{"prev":28,"next":44,"related":62},{"slug":29,"title":30,"description":31,"category":8,"readTime":9,"tags":32,"coverImage":35,"coverImageAlt":36,"heroImage":37,"heroImageAlt":36,"metaTitle":38,"metaDescription":39,"ogImage":40,"noindex":20,"published":21,"publishAt":41,"sortOrder":42,"updatedAt":41,"status":24,"path":43},"philippine-data-centers-where-to-host-nuxt-laravel","Philippine data centers vs APAC cloud: where to host Nuxt and Laravel","No local AWS or GCP region yet — VITRO, Equinix Manila, and Singapore are the real options. An SME guide to residency, latency, and restore.",[33,8,34],"Hosting","Philippines","\u002Fimages\u002Fjournal\u002Fphilippine-data-centers-where-to-host-nuxt-laravel-cover.webp?v=20261013b","Ethernet cables plugged into a network switch","\u002Fimages\u002Fjournal\u002Fphilippine-data-centers-where-to-host-nuxt-laravel-hero.webp?v=20261013b","Where to Host Nuxt + Laravel in the PH | PrimeCode","Where Philippine SMEs should host Nuxt and Laravel — local colocation vs Singapore cloud, data residency, and backups you have actually restored.","\u002Fimages\u002Fjournal\u002Fphilippine-data-centers-where-to-host-nuxt-laravel-og.webp?v=20261013b","2026-09-30T01:00:00.000Z",45,"\u002Fblog\u002Fphilippine-data-centers-where-to-host-nuxt-laravel",{"slug":45,"title":46,"description":47,"category":48,"readTime":9,"tags":49,"coverImage":53,"coverImageAlt":54,"heroImage":55,"heroImageAlt":54,"metaTitle":56,"metaDescription":57,"ogImage":58,"noindex":20,"published":21,"publishAt":59,"sortOrder":60,"updatedAt":59,"status":24,"path":61},"nuxt-3-end-of-life-ssr-ssg-hybrid","Nuxt 3 is end of life. Choose a rendering mode on Nuxt 4","Nuxt 3 support ended 31 July 2026. Stay on Nuxt 4, pick static, server, or client per route, and do not ship a Nuxt 5 preview.","Engineering",[50,51,52],"Nuxt","Rendering","Web","\u002Fimages\u002Fjournal\u002Fnuxt-3-end-of-life-ssr-ssg-hybrid-cover.webp?v=20261013b","HTML and SVG markup on a screen","\u002Fimages\u002Fjournal\u002Fnuxt-3-end-of-life-ssr-ssg-hybrid-hero.webp?v=20261013b","Nuxt 3 Is End of Life. Rendering on Nuxt 4 | PrimeCode","Nuxt 3 support ended 31 July 2026. How to choose SSR, static, or hybrid on Nuxt 4, and why Nuxt 5 is not the October upgrade.","\u002Fimages\u002Fjournal\u002Fnuxt-3-end-of-life-ssr-ssg-hybrid-og.webp?v=20261013b","2026-10-05T01:00:00.000Z",47,"\u002Fblog\u002Fnuxt-3-end-of-life-ssr-ssg-hybrid",[63,65,82],{"slug":29,"title":30,"description":31,"category":8,"readTime":9,"tags":64,"coverImage":35,"coverImageAlt":36,"heroImage":37,"heroImageAlt":36,"metaTitle":38,"metaDescription":39,"ogImage":40,"noindex":20,"published":21,"publishAt":41,"sortOrder":42,"updatedAt":41,"status":24,"path":43},[33,8,34],{"slug":66,"title":67,"description":68,"category":8,"readTime":69,"tags":70,"coverImage":73,"coverImageAlt":74,"heroImage":75,"heroImageAlt":74,"metaTitle":76,"metaDescription":77,"ogImage":78,"noindex":20,"published":21,"publishAt":79,"sortOrder":80,"updatedAt":79,"status":24,"path":81},"dti-ai-scale-up-center-what-msmes-should-build","DTI AI and Scale-Up Center: what MSMEs should actually build","DTI and Converge opened a Makati hub for AI literacy and demos. After the visit: one source of truth, one assisted workflow, integrations you can name.",6,[71,72,34],"AI","MSME","\u002Fimages\u002Fjournal\u002Fdti-ai-scale-up-center-what-msmes-should-build-cover.webp?v=20261013b","Workshop space with people learning digital tools around laptops","\u002Fimages\u002Fjournal\u002Fdti-ai-scale-up-center-what-msmes-should-build-hero.webp?v=20261013b","DTI AI Scale-Up Center — What to Build | PrimeCode","What Philippine MSMEs should build after the DTI and Converge AI Scale-Up Center — systems first, then a thin AI layer, not a booth chatbot.","\u002Fimages\u002Fjournal\u002Fdti-ai-scale-up-center-what-msmes-should-build-og.webp?v=20261013b","2026-09-25T01:00:00.000Z",43,"\u002Fblog\u002Fdti-ai-scale-up-center-what-msmes-should-build",{"slug":83,"title":84,"description":85,"category":8,"readTime":9,"tags":86,"coverImage":87,"coverImageAlt":88,"heroImage":89,"heroImageAlt":88,"metaTitle":90,"metaDescription":91,"ogImage":92,"noindex":20,"published":21,"publishAt":93,"sortOrder":94,"updatedAt":93,"status":24,"path":95},"philippine-firms-ai-ready-not-in-production","Philippine firms look AI-ready. Production results are the real test","The 3 September Tribune piece put numbers on a gap we see in calls: initiatives and KPIs without connected data. How to tell a pilot from production.",[71,8,34],"\u002Fimages\u002Fjournal\u002Fphilippine-firms-ai-ready-not-in-production-cover.webp?v=20261013b","Business leaders in a meeting reviewing AI initiative status","\u002Fimages\u002Fjournal\u002Fphilippine-firms-ai-ready-not-in-production-hero.webp?v=20261013b","PH Firms AI-Ready but Not in Production | PrimeCode","Philippine firms lead AI readiness surveys but stall before production — Tribune 3 Sep 2026, tool sprawl, and a one-workflow test.","\u002Fimages\u002Fjournal\u002Fphilippine-firms-ai-ready-not-in-production-og.webp?v=20261013b","2026-09-21T01:00:00.000Z",41,"\u002Fblog\u002Fphilippine-firms-ai-ready-not-in-production"]