Skip to main content

​
Changelog

Track all changes, improvements, and fixes to Zepeed across releases.

​
Latest Releases

View detailed release notes and download specific versions from the GitHub Releases page.

​
Full Changelog

The complete changelog documenting every change to Zepeed is maintained in the repository:
The authoritative changelog is stored in the Zepeed repository. Always review the latest changelog before upgrading to a new version.
Repository Changelog: View on GitHub

​
Versioning Strategy

Zepeed follows Semantic Versioning:
  • MAJOR version for incompatible API changes
  • MINOR version for new functionality in a backward-compatible manner
  • PATCH version for backward-compatible bug fixes

​
Release Schedule

Zepeed is under active development. Features, APIs, configuration options, and internal behavior may change without notice. Breaking changes can occur between releases as the project evolves.If you depend on Zepeed in production, pin to a specific version and review release notes before upgrading.

​
Breaking Changes

Breaking changes are clearly documented in release notes with the label BREAKING. Before upgrading across major versions, review the following:
  • API endpoint modifications or removals
  • Configuration option changes
  • Database schema changes
  • Authentication mechanism updates
  • Feature deprecations

​
Getting Notified

To stay informed about new releases:
  1. Watch the Repository: Click the “Watch” button on GitHub
  2. GitHub Releases: Subscribe to release notifications
  3. Star the Repository: Show your support and stay engaged with project updates

​
Accessing Previous Versions

All historical versions are available:

​
Upgrade Path

When upgrading Zepeed:
1

Review Changelog

Check the changelog for your current version up to the target version. Note any breaking changes.
2

Read Release Notes

Visit the Releases page for your target version and read the detailed release notes.
3

Test in Staging

Test the upgrade in a staging environment before applying to production.
4

Backup Database

Always backup your database before upgrading.
5

Follow Migration Guide

If provided in the release notes, follow any database migrations or configuration updates.
6

Verify Functionality

After upgrading, verify that all features work as expected in your environment.

​
Migration Guides

For significant releases, dedicated migration guides may be provided. Check the release notes for links to migration documentation.

​
Reporting Issues

Found a bug or issue? Report it on the GitHub Issues page. Include:
  • Current version
  • Steps to reproduce
  • Expected behavior
  • Actual behavior
  • Environment details (OS, PHP version, etc.)