Skip to content

[3.33] Quarkus REST: fix @Context injection for records#53502

Open
FroMage wants to merge 2 commits intoquarkusio:3.33from
FroMage:53477-3.33
Open

[3.33] Quarkus REST: fix @Context injection for records#53502
FroMage wants to merge 2 commits intoquarkusio:3.33from
FroMage:53477-3.33

Conversation

@FroMage
Copy link
Copy Markdown
Member

@FroMage FroMage commented Apr 8, 2026

See #53477

@FroMage FroMage requested a review from a team April 8, 2026 13:47
@quarkus-bot quarkus-bot bot changed the title Quarkus REST: fix @Context injection for records [3.33] Quarkus REST: fix @Context injection for records Apr 8, 2026
@quarkus-bot quarkus-bot bot added the area/rest label Apr 8, 2026
@quarkus-bot
Copy link
Copy Markdown

quarkus-bot bot commented Apr 8, 2026

/cc @aloubyansky (3.33), @gastaldi (3.33), @gsmet (3.33), @jmartisk (3.33), @rsvoboda (3.33)

Copy link
Copy Markdown
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

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

If 3.34 is affected, we should first create a PR against 3.34 and then we will backport to 3.33 later.

@FroMage
Copy link
Copy Markdown
Member Author

FroMage commented Apr 8, 2026

If 3.34 is affected, we should first create a PR against 3.34 and then we will backport to 3.33 later.

Won't main become the next version after 3.34? I'm not following.

@geoand
Copy link
Copy Markdown
Contributor

geoand commented Apr 8, 2026

 Won't main become the next version after 3.34? I'm not following.

No, main is 3.35

@FroMage
Copy link
Copy Markdown
Member Author

FroMage commented Apr 8, 2026

And there's interest in releasing fixes for 3.34 before 3.35? I mean, I don't mind, I'll make another PR 🤷

@FroMage
Copy link
Copy Markdown
Member Author

FroMage commented Apr 8, 2026

Done.

@quarkus-bot
Copy link
Copy Markdown

quarkus-bot bot commented Apr 8, 2026

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 31a8b5e.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@geoand
Copy link
Copy Markdown
Contributor

geoand commented Apr 9, 2026

I don't have the mojo to merge this, so leaving it to @quarkusio/lts-guardians

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.

3 participants