Dependency Updates and Breaking Changes
Modern websites are built on top of many smaller pieces of software called dependencies — libraries and tools written by others that your site relies on. Keeping them current is essential, but occasionally an update changes how something works.
Understanding 'breaking changes' helps explain why some updates take more care than others.
How We Decide When to Update
Not every available update is worth applying the moment it appears. We weigh the benefit — usually a security fix or useful feature — against the risk of a breaking change, and time the update accordingly.
Security-critical updates are applied quickly; larger version jumps are planned, tested and scheduled so your site keeps working throughout.
- Review what the update actually changes.
- Assess the risk of a breaking change.
- Test it on a staging copy first.
- Apply it live once we are confident.
What a Dependency Is
Think of dependencies as the bricks your site is built from. You did not make every brick yourself, but your structure depends on each one being sound and current.
When an Update Breaks Something
A breaking change is an update that removes or alters a feature your site depended on. Updating without checking can cause errors, so we test dependency upgrades before they reach your live site.
- A function your site used may be renamed or removed.
- Default behaviour may change in subtle ways.
- Two dependencies may stop being compatible.
How We Manage the Risk
We read release notes, apply updates on a staging copy first, and run tests to confirm everything still works before going live. This keeps your site current without nasty surprises.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.