release: v1.0.4 — WhatsApp community, changelog, version bump - #87
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@codex review |
|
To use Codex here, create a Codex account and connect to github. |
Summary of ChangesHello @diegosouzapw, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This release, v1.0.4, focuses on enhancing community interaction and ensuring up-to-date documentation and configuration. It introduces a new WhatsApp community channel, comprehensively updates the project's changelog, and bumps the overall version. Additionally, it clarifies environment variable usage for OAuth providers, streamlining developer setup. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request prepares for the v1.0.4 release by updating version numbers, changelogs, and adding a WhatsApp community link. A critical security vulnerability was identified in the .env.example file, where several real OAuth client secrets were committed. These secrets must be revoked and removed immediately. Additionally, minor content duplication was found in the German and Italian README files.
| GEMINI_OAUTH_CLIENT_SECRET=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 | ||
| # GEMINI_CLI_OAUTH_CLIENT_ID= | ||
| # GEMINI_CLI_OAUTH_CLIENT_SECRET= | ||
| GEMINI_CLI_OAUTH_CLIENT_SECRET=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 |
There was a problem hiding this comment.
This appears to be a hardcoded secret. Committing secrets to version control is a critical security risk. Please remove this secret, revoke it, and use a placeholder value in this example file, or revert it to its original commented-out state.
# GEMINI_CLI_OAUTH_CLIENT_SECRET=
| # QWEN_OAUTH_CLIENT_ID= | ||
| # IFLOW_OAUTH_CLIENT_ID= | ||
| # IFLOW_OAUTH_CLIENT_SECRET= | ||
| IFLOW_OAUTH_CLIENT_SECRET=4Z3YjXycVsQvyGF1etiNlIBB4RsqSDtW |
There was a problem hiding this comment.
This appears to be a hardcoded secret. Committing secrets to version control is a critical security risk. Please remove this secret, revoke it, and use a placeholder value in this example file, or revert it to its original commented-out state.
# IFLOW_OAUTH_CLIENT_SECRET=
| IFLOW_OAUTH_CLIENT_SECRET=4Z3YjXycVsQvyGF1etiNlIBB4RsqSDtW | ||
| # ANTIGRAVITY_OAUTH_CLIENT_ID= | ||
| # ANTIGRAVITY_OAUTH_CLIENT_SECRET= | ||
| ANTIGRAVITY_OAUTH_CLIENT_SECRET=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 |
There was a problem hiding this comment.
This appears to be a hardcoded secret. Committing secrets to version control is a critical security risk. Please remove this secret, revoke it, and use a placeholder value in this example file, or revert it to its original commented-out state.
# ANTIGRAVITY_OAUTH_CLIENT_SECRET=
| GEMINI_OAUTH_CLIENT_SECRET=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 | ||
| # GEMINI_CLI_OAUTH_CLIENT_ID= | ||
| # GEMINI_CLI_OAUTH_CLIENT_SECRET= | ||
| GEMINI_CLI_OAUTH_CLIENT_SECRET=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 | ||
| # CODEX_OAUTH_CLIENT_ID= | ||
| # CODEX_OAUTH_CLIENT_SECRET= | ||
| # QWEN_OAUTH_CLIENT_ID= | ||
| # IFLOW_OAUTH_CLIENT_ID= | ||
| # IFLOW_OAUTH_CLIENT_SECRET= | ||
| IFLOW_OAUTH_CLIENT_SECRET=4Z3YjXycVsQvyGF1etiNlIBB4RsqSDtW | ||
| # ANTIGRAVITY_OAUTH_CLIENT_ID= | ||
| # ANTIGRAVITY_OAUTH_CLIENT_SECRET= | ||
| ANTIGRAVITY_OAUTH_CLIENT_SECRET=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 |
There was a problem hiding this comment.
Multiple OAuth client secrets (Gemini, Iflow, Antigravity) have been committed directly to the .env.example file. These appear to be real credentials rather than placeholders, posing a critical security risk. They must be immediately removed, replaced with generic placeholders or commented out, and revoked/rotated in their respective provider consoles.
# GEMINI_OAUTH_CLIENT_SECRET=
# GEMINI_CLI_OAUTH_CLIENT_ID=
# GEMINI_CLI_OAUTH_CLIENT_SECRET=
# CODEX_OAUTH_CLIENT_ID=
# CODEX_OAUTH_CLIENT_SECRET=
# QWEN_OAUTH_CLIENT_ID=
# IFLOW_OAUTH_CLIENT_ID=
# IFLOW_OAUTH_CLIENT_SECRET=
# ANTIGRAVITY_OAUTH_CLIENT_ID=
# ANTIGRAVITY_OAUTH_CLIENT_SECRET=
There was a problem hiding this comment.
Pull request overview
Prepares the v1.0.4 release by bumping package versions, adding a v1.0.4 CHANGELOG entry summarizing prior PRs (#84–#86), and updating READMEs (including translations) with a WhatsApp community link and v1.0.4 references.
Changes:
- Bump
package.json/package-lock.jsonversion from 1.0.3 → 1.0.4. - Add
CHANGELOG.mdentry for v1.0.4 and release tag reference. - Update README + translations with WhatsApp community link and v1.0.4 text updates.
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 13 comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Version bump to 1.0.4 |
| package-lock.json | Lockfile version bump to 1.0.4 (root + package entry) |
| CHANGELOG.md | Adds v1.0.4 release notes and link reference |
| README.md | Adds WhatsApp badge + nav link; updates version references |
| README.pt-BR.md | Adds WhatsApp badge/support link; updates version references |
| README.es.md | Adds WhatsApp badge/support link; updates version references |
| README.ru.md | Adds WhatsApp badge/support link; updates version references |
| README.zh-CN.md | Adds WhatsApp badge/support link; updates version references |
| README.de.md | Adds WhatsApp badge/support link; updates version references (also includes a duplicate bullet) |
| README.fr.md | Adds WhatsApp badge/support link; updates version references |
| README.it.md | Adds WhatsApp badge/support link; updates version references (also includes a duplicate bullet) |
| .env.example | Modified (currently includes committed OAuth secrets — must be removed) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| [](https://chat.whatsapp.com/JI7cDQ1GyaiDHhVBpLxf8b?mode=gi_t) | ||
|
|
||
| [🌐 Website](https://omniroute.online) • [🚀 Quick Start](#-quick-start) • [💡 Features](#-key-features) • [📖 Docs](#-documentation) • [💰 Pricing](#-pricing-at-a-glance) | ||
| [🌐 Website](https://omniroute.online) • [🚀 Quick Start](#-quick-start) • [💡 Features](#-key-features) • [📖 Docs](#-documentation) • [💰 Pricing](#-pricing-at-a-glance) • [💬 WhatsApp](https://chat.whatsapp.com/JI7cDQ1GyaiDHhVBpLxf8b?mode=gi_t) |
There was a problem hiding this comment.
The PR description says the WhatsApp community link was added to the nav bar in all README translations, but only the English README adds it to the nav bar list; the translated READMEs still have no WhatsApp item in their nav line. Either add the WhatsApp nav link consistently to the translated READMEs or adjust the PR description to match what was changed.
|
|
||
| - Many providers don't expose a `/models` endpoint | ||
| - OmniRoute v1.0.3+ includes fallback validation via chat completions | ||
| - OmniRoute v1.0.4+ includes fallback validation via chat completions |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ includes fallback validation via chat completions | |
| - OmniRoute v1.0.0+ includes fallback validation via chat completions |
|
|
||
| - Muitos provedores não expõem endpoint `/models` | ||
| - OmniRoute v1.0.3+ inclui validação via chat completions como fallback | ||
| - OmniRoute v1.0.4+ inclui validação via chat completions como fallback |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ inclui validação via chat completions como fallback | |
| - OmniRoute v1.0.0+ inclui validação via chat completions como fallback |
|
|
||
| - Muchos proveedores no exponen el endpoint `/models` | ||
| - OmniRoute v1.0.3+ incluye validación vía chat completions como fallback | ||
| - OmniRoute v1.0.4+ incluye validación vía chat completions como fallback |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ incluye validación vía chat completions como fallback | |
| - OmniRoute v1.0.0+ incluye validación vía chat completions como fallback |
|
|
||
| - Многие провайдеры не предоставляют endpoint `/models` | ||
| - OmniRoute v1.0.3+ включает fallback-валидацию через chat completions | ||
| - OmniRoute v1.0.4+ включает fallback-валидацию через chat completions |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ включает fallback-валидацию через chat completions | |
| - OmniRoute включает fallback-валидацию через chat completions |
|
|
||
| - Viele Anbieter stellen den `/models` Endpoint nicht bereit | ||
| - OmniRoute v1.0.3+ enthält Fallback-Validierung via Chat Completions | ||
| - OmniRoute v1.0.4+ enthält Fallback-Validierung via Chat Completions |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ enthält Fallback-Validierung via Chat Completions | |
| - OmniRoute enthält Fallback-Validierung via Chat Completions |
|
|
||
| - Beaucoup de fournisseurs n'exposent pas le point de terminaison `/models` | ||
| - OmniRoute v1.0.3+ inclut une validation de secours via chat completions | ||
| - OmniRoute v1.0.4+ inclut une validation de secours via chat completions |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ inclut une validation de secours via chat completions | |
| - OmniRoute inclut une validation de secours via chat completions |
|
|
||
| - Molti provider non espongono l'endpoint `/models` | ||
| - OmniRoute v1.0.3+ include validazione fallback tramite chat completions | ||
| - OmniRoute v1.0.4+ include validazione fallback tramite chat completions |
There was a problem hiding this comment.
This note claims fallback validation via chat completions exists only in v1.0.4+, but the CHANGELOG lists this feature as part of v1.0.0 (“OpenAI-compatible validation — Fallback validation via chat completions…”). Consider removing the version qualifier or correcting it to the earliest version that actually introduced the behavior.
| - OmniRoute v1.0.4+ include validazione fallback tramite chat completions | |
| **Il test di connessione mostra "Invalid" per provider compatibili OpenAI** | |
| - OmniRoute include validazione fallback tramite chat completions |
| # IFLOW_OAUTH_CLIENT_ID= | ||
| # IFLOW_OAUTH_CLIENT_SECRET= | ||
| IFLOW_OAUTH_CLIENT_SECRET=4Z3YjXycVsQvyGF1etiNlIBB4RsqSDtW | ||
| # ANTIGRAVITY_OAUTH_CLIENT_ID= | ||
| # ANTIGRAVITY_OAUTH_CLIENT_SECRET= | ||
| ANTIGRAVITY_OAUTH_CLIENT_SECRET=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 |
There was a problem hiding this comment.
More plaintext OAuth secrets are committed here. Please remove the concrete secret values from .env.example (keep them commented/blank) and rotate/revoke them if they were real.
| - **GitHub**: [github.com/diegosouzapw/OmniRoute](https://github.com/diegosouzapw/OmniRoute) | ||
| - **Issues**: [github.com/diegosouzapw/OmniRoute/issues](https://github.com/diegosouzapw/OmniRoute/issues) | ||
| - **WhatsApp**: [Community-Gruppe](https://chat.whatsapp.com/JI7cDQ1GyaiDHhVBpLxf8b?mode=gi_t) | ||
| - **WhatsApp**: [Community-Gruppe](https://chat.whatsapp.com/JI7cDQ1GyaiDHhVBpLxf8b?mode=gi_t) |
There was a problem hiding this comment.
The WhatsApp link is duplicated in the Support list (two identical - **WhatsApp** bullets). Remove one of them to avoid repetition.
| - **WhatsApp**: [Community-Gruppe](https://chat.whatsapp.com/JI7cDQ1GyaiDHhVBpLxf8b?mode=gi_t) |
… translations (#87) Co-authored-by: diegosouzapw <diegosouzapw@users.noreply.github.com>
Release v1.0.4
Changes
package.jsonand all READMEsFiles Changed (12)
package.json/package-lock.json— version 1.0.4CHANGELOG.md— v1.0.4 entryREADME.md+ 7 translations — WhatsApp link + version refs