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

[PR #1995/2d90c0c5 backport][0.15] Fix Any serializer type regression breaking Ruby bindings #2007

Conversation

pedro-psb
Copy link
Member

No description provided.

@pedro-psb pedro-psb changed the base branch from main to update-ci/0.15 October 29, 2024 12:13
@pedro-psb pedro-psb changed the title Patchback/backports/0.15/2d90c0c53c38b24db435d4654f9eef5c1d05c673/pr 1995 [backports/0.15] Fix Any serializer type regression breaking Ruby bindings Oct 29, 2024
@pedro-psb pedro-psb changed the title [backports/0.15] Fix Any serializer type regression breaking Ruby bindings [PR #1995/2d90c0c5 backport][0.15] Fix Any serializer type regression breaking Ruby bindings Oct 29, 2024
@pedro-psb pedro-psb changed the base branch from update-ci/0.15 to 0.15 October 29, 2024 12:30
@mdellweg mdellweg enabled auto-merge (rebase) October 29, 2024 13:48
@mdellweg mdellweg closed this Oct 29, 2024
@mdellweg mdellweg reopened this Oct 29, 2024
@pedro-psb
Copy link
Member Author

The failure in the tests looks unrelated (it appears in this CI update for example) and the check commit is because we didnt have the latest plugin_template updates.

Should this (and the other backports) be stacked on top of the CI update PRs?

@mdellweg
Copy link
Member

The failure in the tests looks unrelated (it appears in this CI update for example) and the check commit is because we didnt have the latest plugin_template updates.

Should this (and the other backports) be stacked on top of the CI update PRs?

I'm working my way through the CI updates atm. I will rebase this afterwards.

@mdellweg
Copy link
Member

The failure in the tests looks unrelated (it appears in this CI update for example) and the check commit is because we didnt have the latest plugin_template updates.
Should this (and the other backports) be stacked on top of the CI update PRs?

I'm working my way through the CI updates atm. I will rebase this afterwards.

Oh, those arent off the shelf patchback pr's, I will need to ask you to rebase eventually.

@pedro-psb
Copy link
Member Author

Oh, those arent off the shelf patchback pr's, I will need to ask you to rebase eventually.

Sure

@pedro-psb pedro-psb force-pushed the patchback/backports/0.15/2d90c0c53c38b24db435d4654f9eef5c1d05c673/pr-1995 branch from a2033dc to 9a9471a Compare October 31, 2024 14:00
@mdellweg mdellweg enabled auto-merge (rebase) October 31, 2024 14:02
@mdellweg mdellweg merged commit 8bdbe07 into pulp:0.15 Oct 31, 2024
12 checks passed
@pedro-psb pedro-psb deleted the patchback/backports/0.15/2d90c0c53c38b24db435d4654f9eef5c1d05c673/pr-1995 branch October 31, 2024 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants