v0.11.2

What's Changed

• Bugfix/#38 freshrss api broken by @reply2future in #39

Full Changelog: v0.11.1...v0.11.2

v0.11.1

What's Changed

• refactor(configure): set the default field of summary from content … by @reply2future in #33

Full Changelog: v0.11...v0.11.1

Using AI gateway

What's Changed

• Feature/issue#16 support chinese by @reply2future in #17
• Bugfix/issue#18 no whitespace by @reply2future in #19
• Bugfix/issue#21 compatible pathnames by @reply2future in #22
• Feature/issue#20 support 3rd url by @reply2future in #23
• Bugfix/issue#20 config not work by @reply2future in #24
• Feature/issue#25 use gateway api by @reply2future in #27

Full Changelog: v0.5...v0.11

Details

It supports Portkey-AI/gateway so it could support a lot of LLM api because it unified API Signature as OpenAI, and it would solve #25 or to support other new AI API which is not the goal of this project.

You could find the method how to use it from the README.md.

You could also upgrade this version if you are using the OpenAI, it's not the break changes, so nothing you need to do after upgrading.

replace legacy api

Breaking

you need to update the model when you upgrade the extension because the extension replace the legacy api #13 . So you could use gpt-4 or gpt-3 models instead.

References

1. #13
2. https://platform.openai.com/docs/models/model-endpoint-compatibility