feat: exclude .next-bump from dist archives#1
Merged
Conversation
Belt-and-suspenders coverage for the bin/release tag-cutting policy landing in shop-ce: ensures the .next-bump marker file (when used by maintainers to override the default patch bump) never ships in dist archives regardless of install path. One-line addition; no other behavioral change.
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
1 participant
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.
Summary
Single-line addition to
composer.json:Belt-and-suspenders for the
bin/releasetag-cutting policy that lands in o3-shop/shop-ce#121 (issue o3-shop/o3-shop#140). The CLI uses an optional.next-bumpfile at the repo root to let maintainers override the default patch bump per-release. This addition ensures that if a.next-bumpfile gets committed, it never ships in dist archives regardless of install path.One-line, one-time addition. Inert until either a
.next-bumpfile is committed AND a dist archive is built. Safe to merge on its own — no behavioural change today.Test plan
composer validatepasses (no schema regression)🤖 Generated with Claude Code