Skip to content

chore(releasing): update VRL changelog block insertion #23075

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

Merged
merged 1 commit into from
May 19, 2025

Conversation

pront
Copy link
Member

@pront pront commented May 19, 2025

Summary

Recently the release CUE format changed. Now VRL changelog is separate from Vector changelog. This PR updates the prepare script to output the new format.

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.

Notes

  • Please read our Vector contributor resources.
  • Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
  • The CI checks run only after we manually approve them.
    • We recommend adding a pre-push hook, please see this template.
    • Alternatively, we recommend running the following locally before pushing to the remote branch:
      • cargo fmt --all
      • cargo clippy --workspace --all-targets -- -D warnings
      • cargo nextest run --workspace (alternatively, you can run cargo test --all)
      • ./scripts/check_changelog_fragments.sh
  • After a review is requested, please avoid force pushes to help us review incrementally.
    • Feel free to push as many commits as you want. They will be squashed into one before merging.
    • For example, you can run git merge origin master and git push.
  • If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
    run cargo vdev build licenses to regenerate the license inventory and commit the changes (if any). More details here.

References

@pront pront requested a review from a team as a code owner May 19, 2025 19:58
@github-actions github-actions bot added the domain: vdev Anything related to the vdev tooling label May 19, 2025
@pront pront added domain: releasing Anything related to releasing Vector and removed domain: vdev Anything related to the vdev tooling labels May 19, 2025
@pront pront force-pushed the pront/update-prepare-vrl-changelog branch from 41e14e8 to 9a34b90 Compare May 19, 2025 20:01
@github-actions github-actions bot added domain: vdev Anything related to the vdev tooling and removed domain: releasing Anything related to releasing Vector labels May 19, 2025
@pront pront force-pushed the pront/update-prepare-vrl-changelog branch from 9a34b90 to 5f80e16 Compare May 19, 2025 20:02
@pront pront force-pushed the pront/update-prepare-vrl-changelog branch from 5f80e16 to bb9b7f8 Compare May 19, 2025 20:03
@pront pront merged commit bf57582 into master May 19, 2025
3 checks passed
@pront pront deleted the pront/update-prepare-vrl-changelog branch May 19, 2025 20:03
@pront
Copy link
Member Author

pront commented May 19, 2025

It will take a lot of work to properly unit test this. We can see how it works when preparing the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: vdev Anything related to the vdev tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant