Remove release.yml: orchestration moving to saltstack-core-uploader#84
Merged
Conversation
Release-detection and per-repo docs PRs are being centralized in the saltstack-core-uploader repo on the Broadcom GHE, alongside the existing watch-salt-release / saltproject-release flow. Removing this workflow so we have a single source of truth and avoid open-PR drift between this repo and the new orchestrator.
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.
Companion to the removal PRs on the two private docs repos (builddocs#37, salt-project-website#66).
Release-detection and per-repo docs PRs are being centralized in the
saltstack-core-uploaderrepo on the Broadcom GHE, alongside the existingwatch-salt-release/saltproject-releaseflow. Detection already works there for the package-upload path; we're adding a paralleldocs-releaseworkflow that opens PRs and runs post-merge actions across all three docs repos.Removing this in-repo workflow so we have a single source of truth and avoid open-PR drift between this repo and the new orchestrator.
For context on what the centralized orchestrator will generate, the recent manual fix in #83 captures the two content-edit bugs (wrong key renamed in
tools/supported-versions.json, missingannouncements.rstentry) — both will be fixed in the new workflow.