Skip to content

[branch-52] chore: Ignore RUSTSEC-2024-0014 (#20862)#21020

Merged
alamb merged 1 commit intoapache:branch-52from
comphead:b52
Mar 18, 2026
Merged

[branch-52] chore: Ignore RUSTSEC-2024-0014 (#20862)#21020
alamb merged 1 commit intoapache:branch-52from
comphead:b52

Conversation

@comphead
Copy link
Contributor

  • Closes #.
Crate:     generational-arena
Version:   0.2.9
Warning:   unmaintained
Title:     `generational-arena` is unmaintained
Date:      2024-02-11
ID:        RUSTSEC-2024-0014
URL:       https://rustsec.org/advisories/RUSTSEC-2024-0014

Which issue does this PR close?

  • Closes #.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes #123` indicates that this PR will close issue #123.
-->

- Closes #.

```
Crate:     generational-arena
Version:   0.2.9
Warning:   unmaintained
Title:     `generational-arena` is unmaintained
Date:      2024-02-11
ID:        RUSTSEC-2024-0014
URL:       https://rustsec.org/advisories/RUSTSEC-2024-0014
```

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
@github-actions github-actions bot added the development-process Related to development process of DataFusion label Mar 18, 2026
@alamb
Copy link
Contributor

alamb commented Mar 18, 2026

Thank you 🙏

@alamb alamb merged commit 74aaa65 into apache:branch-52 Mar 18, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

development-process Related to development process of DataFusion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants