Fix/ai Providers Docs#8
Merged
Merged
Conversation
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.
This release bumps Waygate to version 0.6.2 and corrects documentation around AI provider API key configuration. The primary documentation change clarifies that all supported AI providers — Mistral, Claude, OpenAI, and Gemini — accept API keys through both environment variables and the WordPress admin UI (Settings → Connectors), resolving potential confusion for site administrators who configure keys interactively rather than via
.envfiles. The version string has been updated inwaygate.phpand a corresponding entry added toCHANGELOG.mdin accordance with the project's version bump checklist.Version and Release Management:
WAYGATE_VERSIONconstant and plugin header inwaygate.phpto0.6.2, reflecting this patch-level documentation fix.## [0.6.2]changelog entry toCHANGELOG.mddocumenting the clarification.Documentation:
README.mdto explicitly state that API keys for all providers can be configured via either environment variables or the WordPress admin UI, removing the implicit assumption that env vars are the only mechanism..envaccess is restricted.Files Changed:
CHANGELOG.md(Modified)README.md(Modified)waygate.php(Modified)