Tracking issue for Q1 2023 DevRel-related work

[seanchen1991]

Background

This issue captures some of the Hermes team's work fielding questions / fulfilling requests from ecosystem users in Q1 of 2023. While many such questions and requests do not lend themselves well to being captured by a GitHub issue, the ones that do are tracked retroactively by this issue.

Q1 Tasks

Beta Give feedback

1. One send packet stuck on Osmosis channel channel-0 to Cosmos-Hub #2993
   A: bug E: osmosis I: rpc O: reliability +4
   
2. Client update error while forking from sovereign to consumer chain #2980
   A: bug +1
   
3. github actions: rust.yml conflicts with integration.yaml in concurrency #2999
   A: bug O: tests +2
   
4. Document which minimum version of Hermes to use for ICS (v1.2+) #3030
   I: documentation I: guide +2
   
5. Hermes can't clear ica packets when they are too much #3024
   A: bug +1
   
6. Fix forward_transfer test to match the updated API #3025
   I: dependencies O: ics29-fee O: tests +3
   
7. Chain-id upgrade fails upgrading IBC client in remote chain #3057
   A: bug +1
   
8. Missing documentation for upgrade clients command #3066
   I: documentation +1
   
9. Hermes cannot get the unbonding period from consumer chains #3112
   A: bug I: dependencies +2
   
10. Deprecate SDK 0.43 support #2347
    I: dependencies +1
    
11. Add query client status command #3124
    I: CLI O: new-feature +2
    
12. Support Cosmos SDK 0.46 and 0.47 chains side by side #2276
    A: blocked I: dependencies I: logic I: protocol I: rpc O: new-feature +6
    

---

For Admin Use

• tracking or okr label (as well as any other appropriate labels) applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged