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

[1.0.3 -> main] merge 5.0.3's version bump through to main for tracking #880

Merged
merged 5 commits into from
Oct 2, 2024

Conversation

spoonincode
Copy link
Member

merges to main #877 and AntelopeIO/leap#2412; no changes, just for tracking purposes

@linh2931
Copy link
Member

linh2931 commented Oct 2, 2024

Should the title be [5.03 -> main]?

Base automatically changed from 102bump_merge_main to main October 2, 2024 22:41
@spoonincode
Copy link
Member Author

Should the title be [5.03 -> main]?

I think this is right -- it's a merge of release/1.0 to main. i.e. the command used to create it was git merge origin/release/1.0. It merged in #877 from 1.0, but #877 also merged in AntelopeIO/leap#2412 from 5.0

Normally we keep the titles the same through all merge commits.. and maybe I should have done that here. It seemed more confusing having [1.0.3 -> main] 5.0.3 version bump though

@spoonincode spoonincode merged commit 725590b into main Oct 2, 2024
36 checks passed
@spoonincode spoonincode deleted the 503bump_merge_main branch October 2, 2024 22:50
@ericpassmore
Copy link
Contributor

Note:start
category: Chores
component: Internal
summary: Aid tracking git commits, by merging Leap v5.0.3 version bump.
Note:end

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.

4 participants