fix(release): repack zip root-level for the Composer registry #14
No files matched your search
@@ -14,6 +14,8 @@ build:
|
|||||||
- AGENTS.md
|
- AGENTS.md
|
||||||
- CLAUDE.md
|
- CLAUDE.md
|
||||||
- QWEN.md
|
- QWEN.md
|
||||||
|
- .config
|
||||||
|
- .gitea
|
||||||
- .claude
|
- .claude
|
||||||
- .scratch
|
- .scratch
|
||||||
- .wayfinder
|
- .wayfinder
|
||||||
|
|||||||
@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
|
|
||||||
|
- The packaged zip no longer contains `.gitea/` and `.config/`.
|
||||||
- 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 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.
|
- 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.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user