docs(ampd): update ampd 1.12 release with v1.12.2

[eguajardo]

I updated the same 1.12 file since that version hasn't been deployed by external verifiers yet

---

Note

Updates Ampd 1.12 release notes to v1.12.2, adding bugfix details and updating links and version strings.

• Docs:
  • Updates releases/ampd/2025-10-03-ampd-v1.12.2.md to v1.12.2:
    • Refreshes title, release link, and ampd --version output to 1.12.2.
    • Expands Background with bugfixes: account sequence desync under high concurrency; shutdown hang.

^{Written by Cursor Bugbot for commit 0923bbe. This will update automatically on new commits. Configure here.}

Greptile Overview

Updated On: 2025-10-03 18:39:16 UTC

Summary

This PR updates the release documentation for Ampd from v1.12.1 to v1.12.2. The change involves renaming the release file and updating all version references, release links, and documentation content to reflect the new v1.12.2 version. The background section has been expanded to include an additional bugfix related to ampd hanging during the shutdown process, complementing the existing fixes for account sequence synchronization issues during high concurrency.

The update follows the established release documentation template structure used across the Axelar contract deployments repository. This type of version documentation is critical for tracking deployment status across different networks (Devnet, Stagenet, Testnet, Mainnet) and providing clear deployment and validation instructions for operators.

According to the PR description, this consolidation to v1.12.2 was necessary because the previous v1.12.1 version had not yet been deployed by external verifiers, making it appropriate to update the same documentation file rather than creating a separate release document.

Important Files Changed

Changed Files

Filename	Score	Overview
releases/ampd/2025-10-03-ampd-v1.12.2.md	5/5	Updated release documentation from v1.12.1 to v1.12.2 with expanded background section and updated version references

Confidence score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects straightforward documentation updates with no code changes
• No files require special attention

Sequence Diagram

sequenceDiagram
    participant User
    participant "Release Manager"
    participant "Binary Repository"
    participant "Verifier Node"
    participant "Axelar Network"
    participant "Axelarscan"

    User->>+"Release Manager": "Request ampd v1.12.2 deployment"
    "Release Manager"->>+"Binary Repository": "Download ampd v1.12.2 binary"
    "Binary Repository"-->>-"Release Manager": "Return binary file"
    
    "Release Manager"->>+"Verifier Node": "Stop current ampd process"
    "Verifier Node"-->>-"Release Manager": "Process stopped"
    
    "Release Manager"->>+"Verifier Node": "Update config with new parameters"
    Note over "Verifier Node": "Add tx_broadcast_buffer_size, tx_confirmation_buffer_size, tx_confirmation_queue_cap"
    "Verifier Node"-->>-"Release Manager": "Config updated"
    
    "Release Manager"->>+"Verifier Node": "Replace ampd binary with v1.12.2"
    "Verifier Node"-->>-"Release Manager": "Binary replaced"
    
    "Release Manager"->>+"Verifier Node": "Start ampd with new binary"
    "Verifier Node"-->>-"Release Manager": "ampd v1.12.2 started"
    
    "Release Manager"->>+"Verifier Node": "Run ampd --version"
    "Verifier Node"-->>-"Release Manager": "ampd 1.12.2"
    
    "Verifier Node"->>+"Axelar Network": "Begin voting and signing operations"
    "Axelar Network"-->>-"Verifier Node": "Operations acknowledged"
    
    "Release Manager"->>+"Axelarscan": "Monitor verifier operations"
    "Axelarscan"-->>-"Release Manager": "Voting and signing status"
    
    "Release Manager"-->>-User: "Deployment completed successfully"

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}