Vector vdev-v0.3.18 released on 03-09-2026
Vector vdev-v0.3.18 is out now. Operators and packagers have an authoritative tag to pin even though the GitHub release body contains no human-readable notes.
See the project’s GitHub Releases page (https://api.github.com/repos/vectordotdev/vector/releases/latest) for the tag and any downloadable assets; treat the tag as the source of truth for code and packaging.
What’s in this release
- The vdev-v0.3.18 tag has been published on the Vector repository; the release body on GitHub is empty.
- The tag should be used as the authoritative reference for code, packaging and image tags where you pin versions.
- Practical guidance and verification steps are recommended: fetch the tag and inspect commits/PRs, review any CHANGELOG.md entries, and verify downloadable assets (checksums, signatures, image digests).
Upgrade notes
- No explicit breaking-change notes appear on the release page; back up configs and state, check the repository CHANGELOG.md and the commit/PR range for vdev-v0.3.18 before upgrading.
- Test vdev-v0.3.18 in staging and follow a rolling upgrade for distributed deployments; pin agents to the vdev-v0.3.18 tag where needed so you can roll back to a known-good tag if required.
If you hit problems, open an issue on the vectordotdev/vector repository and reference the vdev-v0.3.18 tag, include logs and configuration snippets, and report how to reproduce the issue — feedback on real-world upgrades helps everyone.
