Skip to content

Conversation

@jannotti
Copy link
Contributor

Updates to docs for v12

Summary

Test Plan

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @jannotti, 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 pull request focuses on updating the documentation for Algorand's Transaction Execution Approval Language (TEAL) to align with version 12. It encompasses changes to reflect the new AVM bytecode version, introduces new opcodes and transaction/application fields, and provides a comprehensive new documentation file detailing all TEAL v12 opcodes.

Highlights

  • Updated Doc Version: The internal docVersion constant in the opdoc tool has been incremented from 11 to 12.
  • Documentation Version Update: The README.md files have been revised to reflect the current AVM bytecode version as 12.
  • New Opcode: falcon_verify: The falcon_verify opcode has been introduced and its usage documented.
  • New TEAL v12 Fields: RejectVersion has been added as a new transaction field and AppVersion as a new application parameter field, both for TEAL v12.
  • Comprehensive TEAL v12 Opcodes Documentation: A new, dedicated markdown file (TEAL_opcodes_v12.md) has been created, providing detailed documentation for all TEAL v12 opcodes.
  • Syntax Highlighting Improvements: The teal.tmLanguage.json file has been updated to ensure proper syntax highlighting for the newly added RejectVersion and AppVersion fields.
Using Gemini Code Assist

The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@jannotti jannotti changed the title v12 docs Docs: v12 docs Aug 25, 2025
@jannotti jannotti self-assigned this Aug 25, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation for the v12 release. The changes are generally correct, including version bumps and adding new opcodes and fields. I've identified a couple of minor documentation inconsistencies for the new falcon_verify opcode where the return value is not specified in the description, unlike other similar verification opcodes. I've suggested corrections to improve consistency.

@jannotti jannotti merged commit 4bdaacd into algorand:master Aug 25, 2025
38 of 39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants