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

Update CI files for branch 2.14 #1789

Merged
merged 1 commit into from
Nov 9, 2024
Merged

Update CI files for branch 2.14 #1789

merged 1 commit into from
Nov 9, 2024

Conversation

pulpbot
Copy link
Member

@pulpbot pulpbot commented Oct 6, 2024

Automated changes by create-pull-request GitHub action

@lubosmj
Copy link
Member

lubosmj commented Oct 18, 2024

Looks like the bump has helped. The automation will keep overwriting the commit after every update. We can merge this PR with the bump at the end of November.

@dralley dralley merged commit c4486de into 2.14 Nov 9, 2024
12 checks passed
@dralley dralley deleted the update-ci/2.14 branch November 9, 2024 23:27
@dralley
Copy link
Contributor

dralley commented Nov 9, 2024

@git-hyagi Well, I just merged this without seeing the last line of Lubos' comment. Do we need to revert or is it fine? Why should it only be merged at the end of November?

@git-hyagi
Copy link
Contributor

@dralley Oh ... no problem, it is fine. The CI was failing and, as a workaround, we were bumping pulpcore (3.21.6 => 3.22.0) 6acb4da

Satellite will support pulpcore 3.21 until the end of November, so we decided to not merge this to keep compatibility. But checking the PR commit history, it seems like last week we had a new force push (ef30f78) which fixed the issue without bumping pulpcore version.

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.

4 participants