Skip to content

Remove the Gridlight AI Platform community packs (gridlight-1.1.2, gridlight-1.1.3) - #304

Open
mannygridlight wants to merge 1 commit into
spectrocloud:mainfrom
mannygridlight:remove-gridlight-packs
Open

Remove the Gridlight AI Platform community packs (gridlight-1.1.2, gridlight-1.1.3)#304
mannygridlight wants to merge 1 commit into
spectrocloud:mainfrom
mannygridlight:remove-gridlight-packs

Conversation

@mannygridlight

Copy link
Copy Markdown
Contributor

What this does

Removes packs/gridlight-1.1.2 and packs/gridlight-1.1.3 — 12 files, no other references in the repository.

Why

We contributed both packs (#229, #247) and we are withdrawing them: Gridlight is no longer distributing through pack-central. Leaving them listed would point Palette users at a pack we are not maintaining here.

We are also retiring the AWS Public ECR images the packs pull from (public.ecr.aws/q1c5c5i2/gridlight/*). Once that lands, an install from these packs fails at image-pull time, so removing the listing is the honest outcome rather than leaving one that breaks with a confusing error.

Request beyond this PR

This PR only removes the source. Anything already pushed to the Palette public registry by push-packs.yml is on your side — could a maintainer also remove or deprecate the published gridlight pack there? Happy to follow whatever process you prefer; we could not find one documented in the repository.

Thanks, and no criticism of pack-central intended — this is purely a distribution decision on our end.

🤖 Generated with Claude Code

Withdrawing gridlight-1.1.2 and gridlight-1.1.3 at the maintainer's request.
Gridlight is no longer distributing through pack-central, so leaving the packs
listed would point Palette users at a pack we are not maintaining here.

Both were contributed by us (spectrocloud#229, spectrocloud#247). Nothing else in the repository
references them.

The images the packs pull from our public ECR are being retired on the same
schedule, so an install from these packs would not succeed for much longer in
any case — removing the listing is the honest outcome rather than leaving one
that fails at pull time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants