Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 3, 2025

This PR contains the following updates:

Package Change Age Confidence
org.eclipse.jetty:jetty-proxy (source) 11.0.24 -> 12.0.23 age confidence
org.eclipse.jetty:jetty-server (source) 11.0.24 -> 12.0.23 age confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

hashicorp-vault-sonar-prod bot commented Jun 3, 2025

Renovate Jira issue ID: SCAN4NET-526

@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch 5 times, most recently from 90984f1 to af78f13 Compare June 4, 2025 06:35
Copy link
Contributor Author

renovate bot commented Jun 5, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 12.x releases. But if you manually upgrade to 12.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-jetty-monorepo branch June 5, 2025 07:34
@pavel-mikula-sonarsource pavel-mikula-sonarsource restored the renovate/major-jetty-monorepo branch June 5, 2025 07:36
@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch 7 times, most recently from d9c6001 to 0154c70 Compare June 11, 2025 09:49
@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch 2 times, most recently from ea2be8a to a383432 Compare June 19, 2025 06:28
@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch 6 times, most recently from ba30102 to c8f7c16 Compare June 27, 2025 09:46
Copy link
Contributor

@pavel-mikula-sonarsource pavel-mikula-sonarsource left a comment

Choose a reason for hiding this comment

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

LGTM

@pavel-mikula-sonarsource
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavel-mikula-sonarsource pavel-mikula-sonarsource enabled auto-merge (squash) June 27, 2025 10:19
@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch from c8f7c16 to 85a7e35 Compare June 27, 2025 11:07
@pavel-mikula-sonarsource
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavel-mikula-sonarsource
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavel-mikula-sonarsource
Copy link
Contributor

Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The following artifacts could not be resolved: org.eclipse.jetty:jetty-servlet:pom:12.0.22 (absent): Could not transfer artifact org.eclipse.jetty:jetty-servlet:pom:12.0.22 from/to sonarsource-public (https://repox.jfrog.io/artifactory/sonarsource): status code: 401, reason phrase: (401)

@renovate renovate bot force-pushed the renovate/major-jetty-monorepo branch from c3e2ccb to cc8e2d0 Compare July 24, 2025 18:04
@martin-strecker-sonarsource
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@martin-strecker-sonarsource
Copy link
Contributor

@martin-strecker-sonarsource
Copy link
Contributor

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor Author

renovate bot commented Jul 24, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants