Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update testnet channels again #124

Merged
merged 5 commits into from
Feb 5, 2025
Merged

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Feb 5, 2025

Fairly straightforward change: bump the osmo testnet channel.

Testing and review

I'd like to verify that this setting works, in a local build of prax, but have been unable to do so. Documented some suggestions in #80 (comment).

@@ -259,7 +259,8 @@ fn process_chain_config(chain_config: ChainConfig) -> AppResult<Registry> {
.join("assetlist.json");

// Parse the local JSON into the AssetList struct
let data = fs::read_to_string(assetlist_path)?;
let data = fs::read_to_string(assetlist_path.clone()).context(
"failed to read cosmos asset info; did you remember to clone the repo with submodules enabled?")?;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

may this save a future maintainer 10m of hair-pulling 🖖

@conorsch conorsch changed the title chore: update osmo channel on testnet chore: update testnet channels again Feb 5, 2025
This channel was opened this morning by @erwanor, to test the latest
code changes just deployed to the Noble testnet.

Refs penumbra-zone/penumbra#4899
@conorsch conorsch force-pushed the testnet-channels-2025-02 branch from a5f5749 to 70a6090 Compare February 5, 2025 19:19
Copy link

changeset-bot bot commented Feb 5, 2025

⚠️ No Changeset found

Latest commit: 2ba11c3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@conorsch
Copy link
Contributor Author

conorsch commented Feb 5, 2025

Apparently this didn't need to be rebased due to #125, but I've done so anyway. @TalDerei I probably should have advocated for merging #124 first, since #125 contained a changeset. Can you append whatever changeset magic is required here to get both 124 & 125 into the next release?

@conorsch conorsch requested a review from TalDerei February 5, 2025 19:25
Copy link
Contributor

@TalDerei TalDerei left a comment

Choose a reason for hiding this comment

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

we should be able to just manually run pnpm changeset publish after merge to publish v12.2.0 which consumes these changes (think the changeset bot hasn't been detecting changesets because it's in npm/ rather than root)

@conorsch conorsch merged commit cb980e3 into main Feb 5, 2025
7 checks passed
@conorsch conorsch deleted the testnet-channels-2025-02 branch February 5, 2025 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants