Skip to content

Commit

Permalink
Update reserved keywords
Browse files Browse the repository at this point in the history
  • Loading branch information
@svilupp
svilupp authored Sep 15, 2024
1 parent 284fd6b commit 17cea6b
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion src/PromptingTools.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,11 @@ const RESERVED_KWARGS = [
:image_url,
:image_path,
:image_detail,
:model
:model,
:strict,
:json_mode,
:no_system_message,
:aiprefill
]

# export replace_words, recursive_splitter, split_by_length, call_cost, auth_header # for debugging only
Expand Down

2 comments on commit 17cea6b

@svilupp
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

Release notes:

Added

  • Added support for OpenAI's JSON mode for aiextract (just provide kwarg json_mode=true). Reference Structured Outputs.
  • Added support for OpenRouter's API (you must set ENV OPENROUTER_API_KEY) to provide access to more models like Cohere Command R+ and OpenAI's o1 series. Reference OpenRouter.
  • Added new OpenRouter hosted models to the model registry (prefixed with or): oro1 (OpenAI's o1-preview), oro1m (OpenAI's o1-mini), orcop (Cohere's command-r-plus), orco (Cohere's command-r). The or prefix is to avoid conflicts with existing models and OpenAI's aliases, then the goal is to provide 2 letters for each model and 1 letter for additional qualifier (eg, "p" for plus, "m" for mini) -> orcop (OpenRouter cohere's COmmand-r-Plus).

Updated

  • Updated FAQ with instructions on how to access new OpenAI o1 models via OpenRouter.
  • Updated FAQ with instructions on how to add custom APIs (with an example examples/adding_custom_API.jl).

Fixed

  • Fixed a bug in aiclassify for the OpenAI GPT4o models that have a different tokenizer. Unknown model IDs will throw an error.

Commits

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/115228

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.55.0 -m "<description of version>" 17cea6b69501762f075f598f5167c0d6b695c423
git push origin v0.55.0

Please sign in to comment.