Extension releases

Extension releases

Use git-extensions.sh for a phpBB extension. Committed root composer.json must contain a safe vendor/name and a version. The sample archive phpbbmodders-example-1.0.0-dev.zip contains the top folder phpbbmodders/example/. Metadata and files come from local HEAD by default, or the pinned GitHub default-branch commit with --remote.

cd /path/to/extension
git-extensions.sh --create
unzip -l ../git-exported/phpbbmodders-example-1.0.0-dev.zip
git-extensions.sh --create --remote --output /path/to/packages
git-extensions.sh --release --remote --dry-run

After testing the package and reviewing the preview, publish explicitly:

git-extensions.sh --release --remote

For an intentional replacement of an existing version:

git-extensions.sh --release --remote --force --dry-run
git-extensions.sh --release --remote --force

Omit --remote to publish local HEAD; tracked files must be clean and HEAD already pushed. Use --remote --repo OWNER/REPO to select another repository without checking it out. Relative custom output directories are resolved from the current repository root, or the invocation directory outside a checkout.

See all shared options and aliases, remote source selection, and publication rules/recovery. --gh-release remains a publishing alias. Archive layout and export-ignore behavior are unchanged; packaging does not run the project's tests.