Skip to content

Conversation

masih
Copy link
Collaborator

@masih masih commented Oct 6, 2025

Add UCI workflows to integrate version checking and version tagging/release/publish.

Add UCI workflows to integrate version checking and version
tagging/release/publish.
Copy link

codecov bot commented Oct 6, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.59%. Comparing base (323ddfd) to head (3bb8d2a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2445      +/-   ##
==========================================
- Coverage   53.88%   51.59%   -2.30%     
==========================================
  Files        1003     1541     +538     
  Lines       96876   156511   +59635     
==========================================
+ Hits        52203    80749   +28546     
- Misses      40910    69675   +28765     
- Partials     3763     6087    +2324     
Flag Coverage Δ
sei-chain 27.55% <ø> (?)
sei-cosmos 51.64% <ø> (+<0.01%) ⬆️
sei-tendermint 58.73% <ø> (+0.06%) ⬆️
sei-wasmd 51.41% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 819 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@masih masih marked this pull request as ready for review October 6, 2025 16:01
@@ -0,0 +1,3 @@
{
"version": "v6.1.12"
Copy link
Contributor

@yzang2019 yzang2019 Oct 6, 2025

Choose a reason for hiding this comment

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

Is this the next version tag we want? Will that be conflict with existing tag?

Copy link
Contributor

Choose a reason for hiding this comment

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

+1: https://github.com/sei-protocol/sei-chain/releases - if it default to doing nothing if an existing tag exists, then lgtm

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That tag already exists, and because it already exists the UCI does nothing.

This PR simply integrates the UCI versioning. It will not make a tag or a release because both are already present:

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We did the same for sei-db @yzang2019 and here is the build on merge to main: https://github.com/sei-protocol/sei-db/actions/runs/18166672464/job/51710684253

As you can see, tag/release creation is skipped because the tag was already present.

@masih masih enabled auto-merge (squash) October 7, 2025 19:03
@masih masih merged commit f7a5def into main Oct 7, 2025
101 of 104 checks passed
@masih masih deleted the masih/uci-versioning branch October 7, 2025 19:45
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.

3 participants