Releases: weaponsforge/gemini-cli
Releases · weaponsforge/gemini-cli
gemini-cli_v0.0.4
Summary
July 5, 2025
- Chore: force install the "latest" Google Gemini CLI on deployment, #10
- Gemini CLI version: 0.1.9
What's Changed
- chore(GMCLI-10): install latest gemini-cli on deployment by @weaponsforge in #11
- v0.0.4 by @weaponsforge in #12
Full Changelog: v0.0.3...v0.0.4
gemini-cli_v0.0.3
Summary
July 2, 2025
- Docs: include the
GEMINI_MODELin the.env.examplefile and docs, #7 - Chore: remove the **/node_modules glob pattern in the Docker compose file
- Gemini CLI version: 0.1.7
What's Changed
- feat/weaponsforge 7: include the GEMINI_MODEL env by @weaponsforge in #8
- v0.0.3 by @weaponsforge in #9
Full Changelog: v0.0.2...v0.0.3
gemini-cli_v0.0.2
Summary
June 30, 2025
- Fix: uploading security reports in GH security tab - add security write permission in job, #1
What's Changed
- fix/weaponsforge-1: add permissions writing to gh security tab by @weaponsforge in #5
- v0.0.2 by @weaponsforge in #6
Full Changelog: v0.0.1...v0.0.2
gemini-cli_v0.0.1
Summary
June 30, 2025
- Fix: use the "latest" Docker tag name
What's Changed
- fix/weaponsforge-1: docker security scan by @weaponsforge in #4
Full Changelog: v0.0.0...v0.0.1
gemini-cli_v0.0.0
Summary
June 30, 2025
- Initial release
- Deploy the image to Docker Hub on create of new tags/releases
- Docker Hub URL is available at: https://hub.docker.com/r/weaponsforge/gemini-cli
- Use BuildX and scan image during deployment
- Update README
What's Changed
- feat: deploy to docker hub by @weaponsforge in #2
- v0.0.0 by @weaponsforge in #3
New Contributors
- @weaponsforge made their first contribution in #2
Full Changelog: https://github.com/weaponsforge/gemini-cli/commits/v0.0.0