Skip to content

Conversation

fastfadingviolets
Copy link
Contributor

Description

We need to account for upgrade names now being the full version name, as well as provide a real upgrade name when running a nightly build. From now, nightly builds will use either the latest released version as their upgrade name--i.e. assuming that main is just building on top of that release--or will use vNext.0.0 if main has been updated to be a new major version.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • Included the correct type prefix in the PR title
  • Targeted the correct branch (see PR Targeting)
  • Provided a link to the relevant issue or specification
  • Reviewed "Files changed" and left comments if necessary
  • Confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • Confirmed the correct type prefix in the PR title
  • Confirmed all author checklist items have been addressed
  • Confirmed that this PR does not change production code

@mergify mergify bot merged commit 0dcdab6 into cosmos:main Jul 16, 2025
20 checks passed
@fastfadingviolets fastfadingviolets deleted the interchaintest/fix-nightly-versions branch July 16, 2025 15:33
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.

2 participants