Repository navigation
chore: remove release staging and publishing workflows - #16803
Merged
TheRealHaoLiu merged 1 commit intoNov 16, 2026
Merged
TheRealHaoLiu merged 1 commit into
TheRealHaoLiu merged 1 commit into
Conversation
AWX releases are no longer published, so the release pipeline is dead code. Remove the Stage Release and Promote Release workflows along with the files only they used: the draft-release playbook and the release process doc with its screenshots.
rooftopcellist
approved these changes
Nov 16, 2026
|
vfanucci
added a commit
to kestra-io/docs
that referenced
this pull request
Nov 19, 2026
- awx-release-status: align FAQ and timeline with sources, add release pipeline removal (ansible/awx#16803) - configuration-drift: fail the Ansible check on playbook errors (pipefail) - network-change-management: link /docs/concepts/secret directly - servicenow-automation: markdown external links, fix Now Assist wording - fnol: drop duplicate FAQ question - terraform-cloud-alternative: add username to git.Clone
vfanucci
added a commit
to kestra-io/docs
that referenced
this pull request
Nov 19, 2026
* seo(resources): publish seven new resource pages * seo(resources): update vendor documentation links * seo(resources): address review on w47 resource pages - awx-release-status: align FAQ and timeline with sources, add release pipeline removal (ansible/awx#16803) - configuration-drift: fail the Ansible check on playbook errors (pipefail) - network-change-management: link /docs/concepts/secret directly - servicenow-automation: markdown external links, fix Now Assist wording - fnol: drop duplicate FAQ question - terraform-cloud-alternative: add username to git.Clone
djyasin
pushed a commit
to djyasin/awx
that referenced
this pull request
Nov 20, 2026
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
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.
SUMMARY
AWX releases are no longer published, so the release pipeline in this repo is dead code. This removes it:
.github/workflows/stage.yml(Stage Release): built and pushed the versioned image, ran the awx-operator test deployment, and created the draft GitHub release..github/workflows/promote.yml(Promote Release): on release publish, pushed theawx.awxcollection to Galaxy, awxkit to PyPI, and theawx/awx-eeimages to Quay.tools/ansible/stage.yml: the draft-release playbook, called only bystage.yml.docs/release_process.mdand the 16 screenshots underdocs/img/that only it referenced.Nothing else in the tree references the removed files. The development image build (
devel_images.yml) and the make targets it shares with the old pipeline (awx-kube-buildx,build_collection) are untouched.ISSUE TYPE
COMPONENT NAME
STEPS TO REPRODUCE AND EXTRA INFO
Follow-up outside this PR: the repository secrets referenced only by these two workflows are no longer needed once this merges:
PYPI_USERNAME,PYPI_PASSWORD,QUAY_USER,QUAY_TOKEN,GALAXY_TOKEN, andAWX_OPERATOR_RELEASE_TOKEN.Older tags and branches still carry
promote.yml, so removing those secrets (and revoking the credentials behind them) is what fully disables publishing.Summary by CodeRabbit