How klyp/wordpress works
This repository distributes WordPress core as Composer versions; it is not itself a WordPress runtime. The principal workflow checks upstream releases, builds missing version tags, and makes those tags available through Packagist for Composer projects. The README documents the release stages and integrations, but the shell scripts and workflow definitions were not excerpted, so internal implementation details are omitted.
Main entry points: build-release.sh Release builder · sync-releases.sh Release synchronizer · sync.yml Scheduled or manual run · composer.json klyp/wordpress package
Components 13
Release automation
- Scheduled or manual run
.github/workflows/sync.yml - Release synchronizer
bin/sync-releases.sh - WordPress release list
Release publication
- Release builder
bin/build-release.sh - WordPress release archive
- SHA-1 verification
bin/build-release.sh - Generated Composer metadata
bin/build-release.sh - Version tags
- Packagist
Composer consumption
- klyp/wordpress package
composer.json - Core installer plugin
- Installed WordPress core
Other components
- Composer project
Connections 13
- Scheduled or manual run → Release synchronizer: runs
README.md - Release synchronizer → WordPress release list: compares releases
README.md - Release synchronizer → Version tags: checks existing
README.md - Release synchronizer → Release builder: builds missing
README.md - Release builder → WordPress release archive: downloads
README.md - Release builder → SHA-1 verification: verifies checksum
README.md - Release builder → Generated Composer metadata: generates metadata
README.md - Release builder → Version tags: creates and pushes
README.md - Version tags → Packagist: notifies via GitHub
README.md - Composer project → Packagist: requires package
README.md - Packagist → klyp/wordpress package: provides version
README.md - Composer project → Core installer plugin: configures
README.md - Core installer plugin → Installed WordPress core: installs into project
README.md