Vector vdev-v0.3.21 released on 22-09-2026
Vector vdev-v0.3.21 is out now. Operators and teams running Vector should inspect the published release before upgrading because the GitHub release has an empty description and the change appears to be a patch/minor update.
Check the canonical release page on GitHub (https://api.github.com/repos/vectordotdev/vector/releases/latest), review the vdev-v0.3.21 tag and the repository’s compare view, and verify available assets, checksums and CI signals before rolling this out.
What’s in this release
- Published GitHub release for vdev-v0.3.21 contains an empty description; no release notes are provided on the release page.
- Likely a patch/minor update — inspect the Git tag vdev-v0.3.21 and use the compare view (for example versus vdev-v0.3.20) to see commits and merged PRs.
- Check for built artifacts and verification data: fetch the tag (git fetch –tags), inspect package/container registries and CI pipelines, and verify any checksums or signatures before deployment.
Upgrade notes
- No explicit breaking changes are listed in the release; perform compatibility checks by backing up current configs and state, validating configuration schema changes and deprecations, and running the new version in a staging environment first.
- If you encounter regressions, roll back to the previous tag (for example vdev-v0.3.20), restore backups and pinned package/container versions, and follow a canary → staged → full rollout strategy for redeploying.
Please share comments on your upgrade experience — reports of regressions, diagnostics or confirmations help others planning the same move.
