Vector vdev-v0.3.17 released on 02-09-2026
Vector vdev-v0.3.17 is out now. Operators and developers should verify release assets and commits because the upstream release body is empty.
Check the GitHub release page (https://api.github.com/repos/vectordotdev/vector/releases/latest), inspect the vdev-v0.3.17 tag and attached release assets, and bookmark the repository for follow-up notes or patched releases.
What’s in this release
- The upstream release body is empty — there are no published release notes for vdev-v0.3.17.
- Attached release assets are available on the GitHub release page; review them for binaries or other artifacts.
- Reconstruct the changelog by comparing the previous tag to vdev-v0.3.17 (use the GitHub compare view, API endpoints or git log to list commits and merged PRs).
Upgrade notes
- No breaking changes are documented in the release body; before upgrading, back up configuration and persistent state, run the release in a staging environment, validate pipelines and endpoints, confirm CLI and config compatibility (vector –version and config validation), and check for breaking-change PRs between your last deployed tag and vdev-v0.3.17.
- Keep previous binaries and configuration files so you can roll back if needed, and run smoke tests after deployment to confirm expected behaviour.
Please share any issues or observations on the repository’s issue tracker and include vector –version output, relevant configs, runtime logs and the exact tag (vdev-v0.3.17) so maintainers can reproduce the problem.
