Skip to content

fix(provider): iflow provider should use merged provider config#751

Merged
sorrycc merged 1 commit intoneovateai:masterfrom
jhao0413:master
Feb 13, 2026
Merged

fix(provider): iflow provider should use merged provider config#751
sorrycc merged 1 commit intoneovateai:masterfrom
jhao0413:master

Conversation

@jhao0413
Copy link
Contributor

Fix a bug where iflow provider's createModel function was using the static iflowProvider object instead of the merged _provider parameter. This prevented the provider from reading apiKey from config file (provider.iflow.options.apiKey), causing requests to be sent without x-iflow-signature header when IFLOW_API_KEY env var was not set.

Changes:

  • Use _provider instead of iflowProvider in getProviderApiKey call
  • Use _provider instead of iflowProvider in createModelCreator call

This ensures the provider respects user configuration and properly generates authentication signatures for all API requests.

Fix a bug where iflow provider's createModel function was using the
static iflowProvider object instead of the merged _provider parameter.
This prevented the provider from reading apiKey from config file
(provider.iflow.options.apiKey), causing requests to be sent without
x-iflow-signature header when IFLOW_API_KEY env var was not set.

Changes:
- Use _provider instead of iflowProvider in getProviderApiKey call
- Use _provider instead of iflowProvider in createModelCreator call

This ensures the provider respects user configuration and properly
generates authentication signatures for all API requests.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@sorrycc sorrycc merged commit f0e08ab into neovateai:master Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants