Use production API key #3560
Merged
Use production API key #3560
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
cloutiertyler
approved these changes
Nov 3, 2025
egormanga
reviewed
Nov 3, 2025
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.
Description of Changes
Inkeep's API key for the search bar is the staging one instead of production, therefore requests made are failing due to an incorrect referrer.
I've fixed this on
docs/releasequickly after we migrated the new docs but haven't made a PR to add it to master, due to this the change was lost ondocs/releasein the last docs release.I just cherry-picked the commit that I had on my local branch
API and ABI breaking changes
None.
Expected complexity level and risk
1
Testing
Cherry-pick of a commit that was already deployed