Skip to content

Build: switch actions to uv#13

Merged
ank1m merged 1 commit intodevelopfrom
build/switch-actions-to-uv
Mar 2, 2026
Merged

Build: switch actions to uv#13
ank1m merged 1 commit intodevelopfrom
build/switch-actions-to-uv

Conversation

@ank1m
Copy link
Copy Markdown
Collaborator

@ank1m ank1m commented Feb 24, 2026

Switch Github Actions to uv

---
config:
    theme: dark
    gitGraph:
        showCommitLabel: false
        mainBranchOrder: 6
---
gitGraph
    commit id: "0.1.1"
    branch develop order: 2
    checkout develop
    commit id: "0.1.1.dev1.hash###"
    branch nice-feature order: 3
    checkout nice-feature
    commit
    commit
    checkout develop
    merge nice-feature id: "0.1.1.dev2.hash###"
    branch issue-fix order: 1
    checkout issue-fix
    commit
    commit
    checkout develop
    merge issue-fix id: "0.1.1.dev3.hash###"
    branch release/0.2.0 order: 4
    checkout release/0.2.0 
    commit tag: "0.2.0rc1"
    branch bugfix order: 5
    checkout bugfix
    commit
    checkout release/0.2.0
    merge bugfix tag: "0.2.0rc2"
    commit tag: "0.2.0" type: HIGHLIGHT
    checkout main
    merge release/0.2.0
    checkout develop
    merge release/0.2.0
    branch new-feature order: 0
    checkout new-feature
    commit
    commit
    checkout develop
    merge new-feature id: "0.2.0.dev2.hash###"
Loading
  • main, develop, release/* branches are protected from direct pushes
  • All development occurs in short-lived feature or bugfix branches merged via PR
  • A release/X.Y.Z branch is created from develop when a new release is approaching
  • RC tags (X.Y.ZrcN) are created on release/X.Y.Z, triggering Docker image builds and pushes
  • Bugs found during RC validation are fixed in short-lived branches and merged back into the corresponding release/X.Y.Z branch
  • When the release is finalized, a X.Y.Z tag is created on the release/X.Y.Z branch
  • The finalized release/X.Y.Z branch is merged back into both main and develop
  • The develop branch version advances dynamically for the next development cycle

PR Acceptance Checklist

  • Unit tests added/updated and passing.
  • Make develop branch default
  • Protect main, develop, and release/** branches
  • Enable pre-commit.ci Web App for harmony-casper

@ank1m ank1m changed the base branch from main to develop February 24, 2026 20:12
@ank1m ank1m marked this pull request as ready for review February 24, 2026 20:50
Copy link
Copy Markdown
Contributor

@kecunning kecunning left a comment

Choose a reason for hiding this comment

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

Looks good!

Copy link
Copy Markdown
Member

@owenlittlejohns owenlittlejohns left a comment

Choose a reason for hiding this comment

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

I took a quick look at this PR - sorry it took me a moment to get to.

  • I can see pre-commit.ci is running. Nice!
  • I can also see the unit tests have run and are passing.

I checked the repo settings, and the default branch is main still, and I don't see branch rule sets to protect direct pushes to develop, main, and the release/** branches. I may have misunderstood our Slack conversation @ank1m - do you want me to make those changes in the settings? Happy to do so, but I don't want to wade in and do it if you're not expecting me to. Let me know.

@ank1m
Copy link
Copy Markdown
Collaborator Author

ank1m commented Mar 1, 2026

Yes, @owenlittlejohns, if you could please make these two changes for default branch and protected branches, it would be great. We don't have permissions to change branch settings. Thank you!

@owenlittlejohns
Copy link
Copy Markdown
Member

I think I've made the changes you're looking for. Here's the default branch update:

Screenshot 2026-03-02 at 10 34 10 am

And here's the list of target branches for a new ruleset:

Screenshot 2026-03-02 at 10 33 45 am

This rule set prevents deletion and requires PRs to merge into these branches. I think those were the changes you were looking for. I can do a screenshare if you want to take a look through.

@ank1m
Copy link
Copy Markdown
Collaborator Author

ank1m commented Mar 2, 2026

Thank you @owenlittlejohns, it looks good. Could you also activate the checkbox for "Block force pushes" for these branches?

@owenlittlejohns
Copy link
Copy Markdown
Member

Looks like you got that one for free as a default. Here are the current settings:

Screenshot 2026-03-02 at 12 52 55 pm

@ank1m
Copy link
Copy Markdown
Collaborator Author

ank1m commented Mar 2, 2026

awesome, thank you!

@ank1m ank1m merged commit eff23ce into develop Mar 2, 2026
3 checks passed
@ank1m ank1m deleted the build/switch-actions-to-uv branch March 2, 2026 17:57
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.

3 participants