feat: add config for checksum during project build - #1293
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1293 +/- ##
==========================================
- Coverage 53.93% 53.92% -0.02%
==========================================
Files 303 303
Lines 23400 23405 +5
==========================================
Hits 12620 12620
- Misses 10752 10757 +5
Partials 28 28
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Soner (shyim)
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Added two new options to the project config (
.shopware-project.yml) to control extension checksum generation duringshopware-cli project ci:build.disable_checksumswhentrue, the "Generating extension checksums" step is skipped entirely, so nochecksum.jsonfiles are written into the extensions.build.keep_existing_checksumswhentrue, extensions that already ship achecksum.jsonkeep it untouched; extensions without one still get a generated file.Both default to
false, existing behavior is unchanged.Why?
Some extensions already deliver a
checksum.jsonand I want to keep those intact.keep_existing_checksumscovers that case,disable_checksumsis for pipelines that don't want the files generated at all.How was this tested?
new tests added (
internal/shop/config_test.go)Related issue or discussion
No.