Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@mandalbalmukund
Copy link
Contributor

@mandalbalmukund mandalbalmukund commented Oct 10, 2025

Problem

πŸ‘‹ Thanks for opening a pull request! Please include a brief summary of the problem your change is trying to solve, or bug fix. If your change fixes a bug or you'd like to provide context on why you're making the change, please link the issue as follows:

Closes: #ISSUE-NUMBER

Solution

Please describe your change as it relates to the problem, or bug fix, as well as any dependencies. If your change requires a schema change, please describe the schema modification(s) and whether it's a backwards-incompatible or backwards-compatible change, then select one of the following:

Note: All schema changes require discussion. Please link the issue for context.

  • Your change modifies the core OpenLineage model
  • Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).

One-line summary: Upgraded commons-lang3 version to 3.18.0 to fix security vulnerability.

Checklist

  • You've signed-off your work
  • Your pull request title follows our guidelines
  • Your changes are accompanied by tests (if relevant)
  • Your change contains a small diff and is self-contained
  • You've updated any relevant documentation (if relevant)
  • Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
  • You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
  • You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2025 contributors to the OpenLineage project

@mandalbalmukund mandalbalmukund requested a review from a team as a code owner October 10, 2025 09:59
@boring-cyborg
Copy link

boring-cyborg bot commented Oct 10, 2025

Thanks for opening your first OpenLineage pull request! We appreciate your contribution. If you haven't already, please make sure you've reviewed our guide for new contributors (https://github.com/OpenLineage/OpenLineage/blob/main/CONTRIBUTING.md).

@kacpermuda
Copy link
Contributor

kacpermuda commented Oct 10, 2025

@mandalbalmukund , please add the DCO to your commit, click on the failed check for instructions on how to do it

@mandalbalmukund mandalbalmukund force-pushed the common-lang3-cve-fix branch 2 times, most recently from 6e988a5 to 7b0f0a1 Compare October 13, 2025 14:16
@mandalbalmukund
Copy link
Contributor Author

@kacpermuda , thank you very much for suggesting to run DCO. As this PR contains only commons-lang3 changes but the issue #4076 is related to netty version change. So, ideally, it should not be closed and should be done the required changes.

@kacpermuda
Copy link
Contributor

Dbt test failure is unrelated, will be fixed in separate pr

@kacpermuda kacpermuda merged commit e53052e into OpenLineage:main Oct 13, 2025
58 of 60 checks passed
@boring-cyborg
Copy link

boring-cyborg bot commented Oct 13, 2025

Great job! Congrats on your first merged pull request in OpenLineage!

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.

2 participants