This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @hyperlane-xyz/cli@3.12.0

### Minor Changes

-   cc87319: Default to home directory for local registry
- ff221f6: Allows a developer to pass a private key or address to
dry-run, and ensures HYP_KEY is only used for private keys.
- eba3936: Add CLI-side submitter to use SDK submitter from CRUD and
other command modules.

### Patch Changes

-   2b7dfe2: Improve defaults in chain config command
-   Updated dependencies [eba3936]
-   Updated dependencies [69de68a]
    -   @hyperlane-xyz/sdk@3.12.0
    -   @hyperlane-xyz/utils@3.12.0

## @hyperlane-xyz/sdk@3.12.0

### Minor Changes

-   69de68a: Implement aggregation and multisig ISM metadata encoding

### Patch Changes

-   eba3936: Exports submitter and transformer props types.
-   Updated dependencies [69de68a]
    -   @hyperlane-xyz/utils@3.12.0
    -   @hyperlane-xyz/core@3.12.0

## @hyperlane-xyz/utils@3.12.0

### Minor Changes

-   69de68a: Implement aggregation and multisig ISM metadata encoding

## @hyperlane-xyz/core@3.12.0

### Patch Changes

-   Updated dependencies [69de68a]
    -   @hyperlane-xyz/utils@3.12.0

## @hyperlane-xyz/helloworld@3.12.0

### Patch Changes

-   Updated dependencies [eba3936]
-   Updated dependencies [69de68a]
    -   @hyperlane-xyz/sdk@3.12.0
    -   @hyperlane-xyz/core@3.12.0

## @hyperlane-xyz/infra@3.12.0

### Patch Changes

-   Updated dependencies [eba3936]
-   Updated dependencies [69de68a]
    -   @hyperlane-xyz/sdk@3.12.0
    -   @hyperlane-xyz/utils@3.12.0
    -   @hyperlane-xyz/helloworld@3.12.0

## @hyperlane-xyz/ccip-server@3.12.0

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

### Description

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description

uses this github action:
https://github.com/amannn/action-semantic-pull-request

### Description

GKE was complaining that the kube-state-metrics version we were running
with was hitting deprecated APIs, I expect this to fix it.

Some minor changes to the infra setup meant that now the push gateway
has a different service name, kinda annoyingly with a double
`prometheus` in the name. I updated key funder to push to the new
gateway

### Drive-by changes

We no longer use GKE autopilot, so started using the node exporter too

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description

- Added agent config description for Osmosis Mainnet
- Updated infra test to allow agent config chains to be a superset of
infra chains

Taken from @byeongsu-hong's #3766, but with a fixed test

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: byeongsu-hong <hong@byeongsu.dev>

### Description

Found the reason why we never had `trace` level logs in release builds -
the `tracing` crate had a feature flag enabled that would wipe out all
trace calls at compile time :(

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

- Fixes #3823


### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->