Release automation tool#2
Open
OleksiiBulba wants to merge 6 commits into
Open
Conversation
- sync init_repository with origin and add init fallback branch handling - harden release flow with explicit branches, auth validation, remote-branch preflight, clean-worktree checks, and non-zero failures - add missing-release recovery, squash-friendly release notes, and dry-run/status modes - add make targets and cleanup/docs for init, release preview, and clean - add Python test suite and GitHub Actions workflow for script coverage
- Updated the --help test coverage so it only applies to scripts that are meant to be run directly. The test in micro-dev/tests/python/test_scripts.py now checks only: - clean.py - fix.py - init.py - release.py Helper modules like git_shell.py, github.py, git_commands.py, packages.py, packagist.py, and shell.py are no longer part of that --help contract.
- Implemented tag preflight inside the existing release flow.
- Added --force-release to scripts/release.py.
- Added direct-release Make targets with optional FORCE=1 in micro-dev/Makefile.
…from all framework packages;\n- Added script for merging composer requirements from all framework packages to root composer.json;\n- Updated spiral/roadrunner to ^2025.1.13 version;\n- Normalized composer.json;
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
This MR syncs the latest release-tooling improvements from
origin-public/2.xintomicro-php/2.x.The main focus is hardening the multi-repo initialization and release flow for Micro PHP packages, making the tooling safer, more
explicit, and easier to operate for first releases and ongoing package releases.
What Changed
initflow for package repositoriesKey Improvements
Init flow
--from-branchfallback when the target branch does not exist in package repos--push-missing-branchesas an opt-inRelease flow
--dry-runand--status--release-currentfor tag/release creation directly from the base branch--force-releasefor first-line releases and other explicit no-commit release casesTooling and docs
scripts/clean.pyMakefiletargets for preview and direct release flowsscripts/README.mdwith release instructionsWhy
The previous release flow was too easy to misuse:
This MR makes the release tooling much more predictable and operationally safe.
Testing
Notes
This branch is ahead of micro-php/2.x by 5 commits and includes the release-tooling changes needed to support the first 2.x
package releases, including 2.0.0-alpha1.