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

chore(releasing): cherry pick v0.20.1 commits #1187

Merged
merged 2 commits into from
Dec 11, 2024

Conversation

pront
Copy link
Member

@pront pront commented Dec 10, 2024

Summary

Cherry pick patch release commits.

Change Type

  • Bug fix
  • New feature
  • Non-functional (chore, refactoring, docs)
  • Performance

Is this a breaking change?

  • Yes
  • No

How did you test this PR?

Does this PR include user facing changes?

  • Yes. Please add a changelog fragment based on
    our guidelines.
  • No. A maintainer will apply the "no-changelog" label to this PR.

Checklist

  • Our CONTRIBUTING.md is a good starting place.
  • If this PR introduces changes to LICENSE-3rdparty.csv, please
    run dd-rust-license-tool write and commit the changes. More details here.
  • For new VRL functions, please also create a sibling PR in Vector to document the new function.

References

vectordotdev/vector#21992

@pront pront changed the title Pront/cherry pick v0.20.1 commits chore(releasing): cherry pick v0.20.1 commits Dec 10, 2024
@pront pront added domain: releasing no-changelog Changes in this PR do not need user-facing explanations in the release changelog labels Dec 10, 2024
@pront pront added this pull request to the merge queue Dec 11, 2024
Merged via the queue into main with commit 62ac471 Dec 11, 2024
15 of 19 checks passed
@pront pront deleted the pront/cherry-pick-v0.20.1-commits branch December 11, 2024 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: releasing no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants