Skip to content
Zenith Docs

Updating Zenith

This guide will introduce you to the Zenith versioning system and show how to update your project to the latest version.

Versioning

Zenith uses Semantic Versioning to manage the project versions. The version number comprises three parts separated by a dot: MAJOR.MINOR.PATCH. Here’s what each part means:

  • MAJOR - the version introduces breaking changes - usually related to content collections validation or related components. Updating your fork may cause conflicts. You may need to update the content of your resume to match the new requirements.
  • MINOR - the version introduces new features, improvements, and bug fixes that affect Zenith functionality. Updating your fork shouldn’t require additional work, as long as you haven’t modified the default components and utilities provided by Zenith.
  • PATCH - the version introduces bug fixes and improvements related to the developer experience. Updating won’t affect the output resume in any way.

Sometimes, we may introduce features and fixes related to the project’s maintenance (e.g., CI changes, sample content updates). The version number won’t reflect those changes as they don’t affect you.

How to update?

If you’ve forked your copy the Zenith project and want to sync it with the original repository, follow the official GitHub fork syncing guide.