Pugpig Code Freeze: December 2026 to January 2027
What is the code freeze? What does it mean for me? Your questions answered.
Table of Contents
Summary
| What? | When? |
Deadline for change requests |
Friday 20 November 2026 |
Code freeze starts |
Wednesday 9 December 2026 |
Deployments resume |
Week commencing Monday 4 January 2027 |
Please Note:
During the code freeze, Pugpig will not deploy changes to live customer apps or to the Pugpig platform. The only exception is fixes for P1 and P2 support incidents.
Important: Please try and avoid changes that could affect your app(s) during the code freeze:
To minimise the risk of disruption, we strongly recommend that you do not make any changes to your website, CMS, feeds, integrations, configuration, or other systems that could affect the app during the code freeze.
If a change is unavoidable, please discuss it with us in advance so that we can assess the potential impact during the code freeze period.
Key dates
If you want a change to potentially be released before the code freeze, you must submit your request no later than Friday 20 November 2026 for there to be a chance of completion ahead of the Wednesday 9th December freeze.
Submitting a request by this deadline does not guarantee that it will be released before the code freeze. Once we receive your request, we will confirm whether it is expected to go live:
- Before the code freeze, or
- After the code freeze.
Note:
The likelihood of completing a change before the code freeze decreases as the deadline approaches, particularly for larger or more complex changes.
Requests submitted after 20 November 2026 will typically be scheduled for release after the code freeze.
Wednesday 9 December 2026: Code freeze starts
- From this date, the rules in the sections below will apply.
Week commencing Monday 4 January 2027: Deployments resume
- We will restart scheduled deployments/rollouts and app updates during this week.
What is paused during the code freeze?
During the code freeze, the following activities will not take place:
- Professional Services deployments: No customer-specific code, configuration or project work will be deployed to production or live environments.
- Product deployments: No platform changes affecting all customers will be released.
- Non-essential app releases: No new app versions will be submitted to or released through the App Store or Google Play, except where required to resolve a P1 or P2 incident.
What will continue during the code freeze
- P1 and P2 support incidents. We will investigate and fix them as normal, and that includes deploying a fix if one is needed, but these will be unlikely to be required due to the freeze, assuming minimal changes made on your side that could affect the app.
- Preparing January releases. We will keep building apps and doing Professional Services work during the freeze. That work will not be deployed or released to production/live set ups until the freeze ends. We are happy to deploy to staging environments for testing.
What counts as P1 and P2?
The definitions come from our Support Policy:
Priority |
Description |
Typical examples |
P1: Critical |
App does not function at all |
App shows no content; timelines do not load; editions not publishing; breaking news or live blogs not publishing; widespread login issues |
P2: High |
App functionality is severely compromised |
Timelines or editions not updating; users unable to register; users unable to make in-app purchases |
All other issues (P3 and P4) will be logged, looked at and resolved where possible, but any fix that needs a deployment will be released after the freeze ends.
For full details, see:
What we ask of you
We strongly recommend that you do not make changes on your side that could affect your app during the code freeze, for example:
- Changes to your website, content feeds or CMS output used by the app
- Changes to login, subscription or paywall systems
- Changes to advertising or analytics setup
If you have to / plan to make a change like this, please tell us by Friday 20th November 2026 at the very latest so we can assess risk and make plans/judgements on how best to proceed.
Frequently asked questions
- Can I get an exception to the code freeze? No. The only exception is fixing a P1 or P2 incident, as defined in our Support Policy.
- Will Pugpig Support still be available? Yes. You can raise tickets as normal. P1 and P2 incidents will be fixed. P3 and P4 issues will be logged and resolved where possible. However, any P3/P4 fix that needs a deployment will be released after the freeze.
- How do I report a P1 or P2 incident during the freeze? Email support@pugpig.com, with “Urgent” in the subject line. Please include app logs, screenshots or recordings, the devices affected, scope and scale of the issue, when it started, and the steps to reproduce it. See How to use Critical Support for details.
- Can my content still be published during the freeze? Yes. The code freeze does not affect editorial publishing. Articles, timelines and editions will keep updating as normal.
- Will you keep working on my project during the freeze? Yes. We will keep building and preparing January releases. Nothing will be deployed or released until the freeze ends.
- When exactly will deployments restart? During the week commencing Monday 4th January 2027. Your Customer Success Manager or Project Manager will confirm when your release is scheduled, or you will be informed on your support ticket.
- Can I release my own changes during the freeze? We strongly recommend that you don't make changes that could affect your app. If something goes wrong, our ability to deploy a fix is limited & you may be asked to roll back any changes through this period to fix any issues that come from changes on your side.
- Who do I contact with questions? Your Customer Success Manager or our support team at support@pugpig.com.


