haylanandClaude Bot
c08d27c8e1
Gitea's registry answered 400 'composer.json file is missing' for the shopware-cli zip (single top-level folder). Repack the same prebuilt content with composer.json at the root. Drop the tag-exists skip guard so a half-finished release can be re-run; reuse an existing release/asset. Bump to 0.1.1. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
77 lines
3.0 KiB
Markdown
77 lines
3.0 KiB
Markdown
# Changelog
|
|
|
|
All notable changes to AeonDumpManager will be documented in this file.
|
|
|
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
|
## [Unreleased]
|
|
|
|
## [0.1.1] - 2026-10-04
|
|
|
|
### Fixed
|
|
|
|
- Release pipeline: the Composer registry rejected the packaged zip (`composer.json file is missing`) because `shopware-cli` zips wrap everything in a top-level folder. The same prebuilt content is now repacked root-level for the registry upload.
|
|
- Release steps are idempotent (existing release and asset are reused, registry 409 counts as published) and the "tag exists -> skip" guard is gone, so a failed release can be re-run to completion.
|
|
|
|
## [0.1.0] - 2026-10-03
|
|
|
|
### Changed
|
|
|
|
- Services and routes are now configured in YAML; the plugin requires PHP `^8.2`.
|
|
- Release pipeline: the packaged `shopware-cli` zip (with prebuilt assets) is validated and used for both the Gitea Release and the Composer registry; the release is created through the Gitea API after packaging, so a failed build no longer leaves an orphan tag.
|
|
- New PR checks: `shopware-cli` validate, package build and phpunit.
|
|
|
|
### Added
|
|
|
|
- Dedicated `aeon_dump_manager` monolog channel; dump jobs, deletions and purges are logged.
|
|
- Extension icon and `.config/shopware-extension.yml`.
|
|
|
|
### Removed
|
|
|
|
- Empty plugin lifecycle overrides.
|
|
|
|
## [0.0.5] - 2026-09-21
|
|
|
|
### Fixed
|
|
|
|
- Changed namespace
|
|
|
|
## [0.0.4] - 2026-09-21
|
|
|
|
### Fixed
|
|
|
|
- Published Composer packages are now linked to this repository (previously the release workflow
|
|
published them without a repository association, so they did not appear under the repo's
|
|
Packages tab).
|
|
|
|
## [0.0.3] - 2026-09-17
|
|
|
|
### Added
|
|
|
|
- Filter the dump list by date range and sort by date or size; dates use Shopware's locale-aware
|
|
formatting.
|
|
|
|
## [0.0.2] - 2026-09-21
|
|
|
|
### Added
|
|
|
|
- Automated release pipeline: a pre-merge check enforcing a semver version bump and a matching
|
|
CHANGELOG entry on every PR into `main`, and a post-merge workflow that tags the release,
|
|
packages the plugin with `shopware-cli`, publishes a Gitea Release with the packaged zip, and
|
|
publishes the package to this Gitea instance's Composer registry.
|
|
- `main` is now a protected branch: no direct pushes, merges require the version/changelog check
|
|
to pass.
|
|
|
|
## [0.0.1] - 2026-09-15
|
|
|
|
### Added
|
|
|
|
- List, create, delete, and download gzip-compressed SQL dumps from a Settings admin page (async
|
|
creation with a polling progress bar) or via the `aeon:dump:list`, `aeon:dump:create`, and
|
|
`aeon:dump:remove` console commands (sync). Dumps are produced with `mysqldump`/`mariadb-dump`
|
|
(auto-detected, overridable via `dumpBinaryName`) and stored in the plugin's private filesystem.
|
|
- Retention controls: `maxDumps` purges the oldest dump when the limit is reached; `retantionDays`
|
|
purges expired dumps and stale job rows via a scheduled task.
|
|
- ACL-gated by `aeon_dump_manager.viewer`/`.creator`/`.deleter`, enforced client- and server-side.
|