Zapier Release Notes

Zapier Release Notes

Glossary:

Version Numbers X.X.X

We use semantic versioning for product release management, for example, 1.3.6.

In that sequence the first digit represents a major release, normally signified by an architectural change. The second digit represents a new feature or upgrade that doesn’t affect the product’s architecture, essentially a minor version. The third digit represents a patch release. Patch releases are made on a weekly basis and include bugs and minor features, unless there is an urgent fix to be addressed, in which case a hot fix will be released (denoted by a set of fourth digits, for example 1.3.6.ab7c4).

Potential Actions Needed

This is Always at the top.

This signifies that a change has been made that could lead to breaks if the steps provided are not taken.

This is a warning to let you know that there is no guarantee that this update will work as default

Hot Fix

This is Always at the top and is a type of update.

This is a unscheduled update to fixes problems that arise outside of the normal development life cycle.

Features

This is usually at the top.

This is where any updates to our product that change how it is used or how it functions are shown.

Bugs

This is usually at the top.

This is where any updates that fixed a break from a previous update are shown.

On radar

This is usually in the middle.

This is where any bugs that we are aware of but have not been fixed yet are shown. This will only show the newest that we are aware of not all.

Improvements

This is usually in the middle.

This is where any improvements to our software that is not a feature is shown. I.E. Something is faster, easier to use, style changes, etc.

Breaking Changes

This is usually at the bottom

This is where changes that would cause a potential action required to be made are shown in a more verbose way.

Deprecation

This is usually at the bottom

This is where any changes that would remove, functionality of our software will be shown.