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.

Sign up for GitHub

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

Jump to bottom

[irods/irods#6412] Bump version to 4.3.1 (main) #122

Merged
merged 1 commit into from
Oct 5, 2023
Merged

[irods/irods#6412] Bump version to 4.3.1 (main) #122

merged 1 commit into from
Oct 5, 2023

Conversation

korydraughn
Copy link
Contributor

No description provided.

@trel
Copy link
Member

trel commented Oct 5, 2023

this seems correct - i see three other PRs that we should eyeball as well.

alanking
alanking reviewed Oct 5, 2023
View reviewed changes
Copy link
Contributor

@alanking alanking left a comment

Choose a reason for hiding this comment

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

@trel - Should we look at those before bumping?

@korydraughn
Copy link
Contributor Author

2 of those are for 4.2. The other one is the stage 2 refactor effort planned by @SwooshyCueb.

I think we're good.

alanking
alanking approved these changes Oct 5, 2023
View reviewed changes
Copy link
Contributor

@alanking alanking left a comment

Choose a reason for hiding this comment

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

Then # it, I say

@korydraughn
Copy link
Contributor Author

#'d

@alanking alanking merged commit 6e6795c into irods:main Oct 5, 2023
1 of 2 checks passed
@korydraughn korydraughn deleted the 6412.m branch October 5, 2023 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alanking alanking alanking approved these changes

@SwooshyCueb SwooshyCueb SwooshyCueb approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@korydraughn @trel @SwooshyCueb @alanking