Skip to content
This repository was archived by the owner on Jul 22, 2026. It is now read-only.

ASUWebPlatforms/composer-packages-test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

composer-packages-test

TEST REPOSITORY. This is a throwaway harness for validating the Satis-replacement pipeline before it goes live. The publisher is ASUWebPlatforms/webspark-composer-test. Do not point production consumers here. The production repo will be ASUWebPlatforms/composer-packages.

A static Composer repository for ASU Webspark packages. Package artifacts are stored as GitHub Release assets; the packages.json metadata is served from GitHub Pages. You can view the current metadata at https://asuwebplatforms.github.io/composer-packages-test.

This is a custom repository registry of composer packages, similar to one generated by Satis, but simpler and tailored for ASU Webspark. The packages.json file is generated by scripts/merge-packages-json.sh from metadata derived directly from each package's own composer.json at build time, and accumulated here (committed) on every publish.

Consumer usage (test)

Add the repository to your project's composer.json:

{
    "repositories": [
        { "type": "composer", "url": "https://asuwebplatforms.github.io/composer-packages-test/" }
    ]
}

Then require packages as normal:

composer require asuwebplatforms/asu_brand

Notes for consumers

  • The repository must remain public for unauthenticated composer install.
  • Branch builds are published as the dev-main version. Require them with composer require asuwebplatforms/asu_brand:dev-main.
  • Release builds are published as the version in composer.json. Require them with composer require asuwebplatforms/asu_brand:1.0.0 (or whatever the version is).

How it works

  1. A push/tag on webspark-composer-test runs the publish workflow there.
  2. Each package subdirectory is zipped and uploaded as a Release asset on this repo.
  3. The publish workflow fires a single repository_dispatch carrying the new versions' metadata.
  4. rebuild.yml here merges that metadata into packages.json, commits it, and deploys to Pages.

Files

  • packages.json — the accumulator of record (auto-generated; do not hand-edit).
  • scripts/merge-packages-json.sh — merges new version records into it.
  • .github/workflows/rebuild.yml — rebuild + Pages deploy.

About

⛔️ DEPRECATED: No longer used.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages