fix: only publish CE marketplace listing for stable releases#258
Open
bpmct wants to merge 1 commit into
Open
Conversation
Gate the AWS Marketplace CE submission step on stable channel and add an early ECR image check to skip already-published versions.
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.
The CE marketplace submission from #255 runs on every release dispatch. It should only run for stable releases (the CE listing tracks stable, not mainline).
Two changes:
release_channel == 'stable'(from thecoder/coderdispatch payload) or on manualworkflow_dispatch.describe-imagescheck insubmit_ce.shexits cleanly if the image tag already exists in ECR, making the script idempotent.Context
coder/coder'srelease.yamlsends arepository_dispatchwithrelease_channel(mainline,stable,rc) to this repo. The GitHub API's/releases/latestendpoint always points to stable (set viaMakeLatest: "true"during promotion). The CE listing should only update on stable promotions — mainline releases would just create noise in the marketplace.The ECR check is the single source of truth for "already processed" — no external state needed. If the workflow is re-run for the same version, it skips cleanly.
Generated by Coder Agents.