Defer hosted API: remove automatic deployment trigger and require manual confirmation - #16
Merged
Merged
Conversation
…s and production checks
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.
Owner approved peripheral closeout after removing the isolated Railway trial. Make deploy.yml workflow_dispatch-only on main with explicit deploy-hosted-api confirmation. Keep existing config/readiness gates, test/release/container workflows and runtime code intact. Update deployment docs to distinguish self-hostable 0.8.5 from an unavailable maintainer-operated production endpoint; retain all key/rotation/migration safeguards. Add three no-network workflow guard tests. No secret access, provisioning, deployment, version bump, frozen draft or Prooftask changes.