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

[3.15] 3.15.2 backports 1 #43985

Merged
merged 47 commits into from
Oct 30, 2024
Merged

[3.15] 3.15.2 backports 1 #43985

merged 47 commits into from
Oct 30, 2024

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Oct 21, 2024

Please don't merge, I will merge it myself.

@gastaldi @rsvoboda @aloubyansky here is the first round following the meeting we had next week.

geoand and others added 30 commits October 18, 2024 14:08
I had to set this in a sample, and it took me
a few tries to come up with the proper syntax
for passing multiple parameters as the description
of the property was completely absent

(cherry picked from commit a417d6f)
- and proceed to the next route

(cherry picked from commit 44ce63e)
This is the same exact support as exists for normal
Resource methods

Fixes: quarkusio#43422
(cherry picked from commit 898b038)
Fixes quarkusio#43474

Signed-off-by: Chris Laprun <[email protected]>
(cherry picked from commit 243b4d3)
Signed-off-by: Marc Nuri <[email protected]>
(cherry picked from commit f1ffb87)
Fixes quarkusio#42237

(cherry picked from commit 9cf2c80)
We use the ones coming from the push events.
Related to quarkusio#43559

(cherry picked from commit e788d0e)
This can be useful when pushing small iterations to a pull request.

It is limited to pull requests only and only for the Initial JDK build.
We will check if it improves things and the size of the cache.

Related to quarkusio#43559

(cherry picked from commit 287ce49)
The existing method leads to a "Failed to index" warning
being printed when the class doesn't exist

(cherry picked from commit c69e206)
(cherry picked from commit 0b4d729)
Fixes quarkusio#41813

Signed-off-by: Martin Bartoš <[email protected]>
(cherry picked from commit 4c49feb)
(cherry picked from commit fcc95de)
(cherry picked from commit e9fa0c9)
@quarkus-bot quarkus-bot bot added area/dependencies Pull requests that update a dependency file area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/docstyle issues related for manual docstyle review area/documentation area/funqy area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure area/kafka-streams area/kubernetes area/maven area/netty area/oidc area/platform Issues related to definition and interaction with Quarkus Platform area/qute The template engine area/rest area/rest-client area/vertx labels Oct 21, 2024
@gtroitsk
Copy link

@gsmet can you please backport #43884 also?

@quarkus-bot
Copy link

quarkus-bot bot commented Oct 21, 2024

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit c3e5d45.

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

Copy link

github-actions bot commented Oct 21, 2024

🙈 The PR is closed and the preview is expired.

@rsvoboda
Copy link
Member

@gsmet can you please backport #43884 also?

There will be another round of backports @gtroitsk. I expect that backport can wait for round 2. Please let us know if there is something pressing.

@gtroitsk
Copy link

@gsmet can you please backport #43884 also?

There will be another round of backports @gtroitsk. I expect that backport can wait for round 2. Please let us know if there is something pressing.

Sure, this way no pressing atm

@quarkus-bot
Copy link

quarkus-bot bot commented Oct 21, 2024

Status for workflow Quarkus CI

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

✅ 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.

You can consult the Develocity build scans.

@rsvoboda
Copy link
Member

CI is green 🎉

@rsvoboda
Copy link
Member

@gsmet I think this could be merged, it has some docs fixes that could be used downstream.

@MichalMaler
Copy link
Contributor

@gsmet I think this could be merged, it has some docs fixes that could be used downstream.

@rsvoboda
The fixes we need are

@gsmet gsmet merged commit 70308b3 into quarkusio:3.15 Oct 30, 2024
56 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/amazon-lambda area/config area/core area/dependencies Pull requests that update a dependency file area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/docstyle issues related for manual docstyle review area/documentation area/funqy area/infra internal and infrastructure related issues area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure area/kafka-streams area/kubernetes area/maven area/netty area/oidc area/platform Issues related to definition and interaction with Quarkus Platform area/qute The template engine area/rest area/rest-client area/vertx
Projects
None yet
Development

Successfully merging this pull request may close these issues.