Vector vdev-v0.3.16 released on 27-08-2026
Vector vdev-v0.3.16 is out now. The release was published as a tag/asset point with an empty release body, so operators should verify assets, tags and CI artefacts directly before upgrading.
Check the release page on GitHub (https://api.github.com/repos/vectordotdev/vector/releases/latest) and the repository metadata for full details on assets and the changelog prior to any deployment.
What’s in this release
- The release tag vdev-v0.3.16 was published but the release description is empty — treat it as a published tag/asset point and verify release assets and CI artefacts on the release page or via git/CLI.
- Changelog needs reconstruction from repo metadata: fetch tags and run git log vdev-v0.3.15..vdev-v0.3.16 –oneline, review merged PRs or use gh release view to enumerate changes and check commit messages for bugfixes, dependency bumps, performance tweaks or documentation updates.
- Classed as a patch-level v0.3.x release — test in a staging environment, back up configs and validate configuration compatibility before rolling out to production.
Upgrade notes
- No explicit breaking changes are documented in the release body; still back up current configs and state and run configuration validation (for example: vector config lint) to confirm schema compatibility before upgrading.
- If you need to roll back, restore from your backups and redeploy the previous tag (for example vdev-v0.3.15); verify checksums and image/binary tags match the release assets when switching versions.
If you try the release, share comments or problems on the Vector GitHub issue tracker and include the exact version, reproduction steps, config files, logs, and the output of vector –version and vector config validation; link to the release URL and any failing CI/artifact IDs to speed troubleshooting.
