Shipped · DevOps and infrastructure

What velero-io/velero shipped

The public repository of Velero · github.com/velero-io/velero

Written by FoxPlug from the repository's own releases; not affiliated with Velero. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/velero-io/velero; Velero did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for velero, free

Week of November 2, 2026

What shipped

Why it matters

This week brings the first release candidate for 1.19, including a new block data mover, while security and correctness fixes address image vulnerabilities and backup sync handling of incomplete or tampered data. Documentation and release notes for 1.19 are in place, and developer tooling and E2E coverage were improved.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Velero v1.19.0-rc.1 is out with a block data mover. This week also fixed image vulnerabilities and bumped Go to 1.27, reverted the API module split, and made backup sync ignore incomplete PVB from BSL. Tilt dev setup now works on clean checkouts and arm64.

Post for LinkedIn

Velero v1.19.0-rc.1 is available, introducing a block data mover for container storage. Alongside the release candidate, this week's changes fixed seven image vulnerabilities and bumped Go to 1.27, reverted the API module split so pkg/apis is part of the root module again, and updated backup sync to ignore incomplete PVB to avoid unexpected execution from tampered BSL data. The Tilt development setup now works from a clean checkout and on arm64, and E2E tests gained a DATA_MOVER parameter.

Week of October 26, 2026

What shipped

Why it matters

This week improves failure handling on the paths that most often go wrong in practice: deleting backups whose tarball or snapshot is already gone, and reading logs while an operation is still finishing. Operators also get new control over data mover upload and download concurrency, and plugin authors can now reuse the built-in resource modifier implementation.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: logs for backups and restores in Finalizing are now readable, GCS object-not-found and stale kopia snapshots are handled on delete, parallel upload and download control lands for the file system and block data movers, and a block uploader ioctl fix for other architectu

Post for LinkedIn

This week in Velero: velero backup logs and velero restore logs now work while a backup or restore is in Finalizing or FinalizingPartiallyFailed. Backup deletion handles two common failures better, recognizing the GCS object-not-found error and treating a kopia snapshot still missing after a repo refresh as deleted. Parallel upload and download control was added for the file system and block data movers. The block uploader no longer hardcodes a BLKZEROOUT ioctl request number that is architecture specific. Backup sync, delete and restore now ignore invalid PodVolumeBackup uploaders in the Restic deprecation work. The resourcemodifiers package moved to pkg/ so external restore item action plugins can import it. CodeQL analysis was added for the Go code, and Dependabot now groups Go security

Week of October 19, 2026

What shipped

Why it matters

This week fixes a restore bug that could skip resources and makes version mismatch warnings clearer for anyone running a client and server on different releases. The e2e changes mean CI runs more of the snapshot and namespace-mapping cases on kind and can no longer report a passing run that selected no specs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: fixed a restore resource priorities bug that could skip resources, clearer client and server version mismatch warnings, and e2e runs that fail when a label filter selects nothing.

Post for LinkedIn

This week in Velero: fixed a restore resource priorities aliasing bug that could skip restoring resources when a dash appears in the middle of the priority list. Velero version now explains that compatibility is not guaranteed when client and server major or minor versions differ and shows which side to update. The e2e suite now matches --features as the comma-separated list it is and fails when a label filter selects no specs, and Kibishii snapshot and namespace-mapping cases now run on kind under CSI. Make serve-docs works again on buildx setups.

Week of October 12, 2026

What shipped

Why it matters

This week brings the CSI e2e cases onto kind in CI, so that path is now exercised automatically, and points Kibishii at the matching overlay. CI should also see fewer module download failures now that Go modules are cached between kind e2e jobs. Restore users get a new option for bypassing the same volume handle pre-flight check, and the remaining changes move repository references and docs to the velero-io organization.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: CSI e2e cases now run on kind in CI, Kibishii uses the kind-csi overlay when CSI is enabled, and kind e2e jobs reuse cached Go modules. Restore adds AllowExistingVolumeMismatch, and docs and issue URLs move to velero-io.

Post for LinkedIn

This week in Velero: the CSI end-to-end cases now run on kind in CI, completing the remaining piece of the kind CSI work. The Kibishii installer points at the kind-csi overlay when CSI is enabled, and the KIBISHII_COMMIT pin moves to the commit that adds it. Kind e2e jobs now reuse cached Go modules across jobs instead of downloading every module on each run. Restore adds AllowExistingVolumeMismatch for bypassing the same volume handle pre-flight check. The CSI-on-kind docs now use the storage-class-file flag, three broken anchor links in the main docs are fixed, and issue URLs and references move from vmware-tanzu to velero-io.

Week of October 5, 2026

What shipped

Why it matters

This week touched backup correctness and e2e reliability. Crashes, context propagation, path checks, and clearer warnings reduce surprises during real backups and restores, while more CSI and VolumeGroupSnapshot e2e coverage and fixed workflow caching make the tests more trustworthy.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: fixed a Zip Slip boundary check, a concurrent map write crash in pvcPvMap, context propagation in backup prep, and a stale repo metadata cache. Added a warning when snapshot volume data is not restored, plus CSI and VolumeGroupSnapshot e2e coverage.

Post for LinkedIn

This week in Velero: archive extraction now rejects sibling directories with a proper path boundary check, and a concurrent map write crash in pvcPvMap was fixed. Backup request preparation propagates the reconciler context, and the repository metadata cache duration and stale problem was corrected. Users now see a warning when snapshot-based volume data of an existing PVC is not restored. On the e2e side, CSI snapshot verification and VolumeGroupSnapshot coverage were added, StorageClass definitions became configurable, and the MinIO image cache key in the kind workflow was fixed.

Week of September 28, 2026

What shipped

Why it matters

V1.18.4 addresses a critical backup queue issue that could leave backups permanently stuck. Improvements to VolumeGroupSnapshot handling and VGDP soothing enhance reliability for users relying on CSI snapshots and volume group backups. Better API version detection makes Velero more compatible across Kubernetes distributions.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Velero v1.18.4 is out with a fix for backup queues getting stuck. VolumeGroupSnapshot API version detection now works across distributions.

Post for LinkedIn

Velero v1.18.4 is now available. This release fixes a critical issue where backup queues could become permanently stuck, improves VolumeGroupSnapshot handling by detecting API versions at runtime, and defers cleanup operations until backup finalization. Enhanced compatibility across Kubernetes distributions including OpenShift.

Week of September 21, 2026

What shipped

Why it matters

V1.18.4-rc.1 and v1.18.3 releases address critical issues with backup queue handling and CLI installation. The namespace label selection feature in resource policies gives users more flexible backup filtering options. Multiple context propagation and CVE fixes improve reliability and security.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Velero v1.18.3 and v1.18.4-rc.1 shipped this week with backup queue fixes, namespace label selection in resource policies, and CVE updates.

Post for LinkedIn

This week Velero released v1.18.3 and v1.18.4-rc.1, bringing important reliability and security improvements. Key additions include namespace selection by label in resource policies for more flexible backup filtering, fixes for backup queue handling, and CVE patches. The v1.18.4-rc.1 release candidate is now available for testing.

Week of September 14, 2026

What shipped

Why it matters

This week's changes address critical issues in in-place restore operations, backup queue management, and CSI volume handling that improve reliability and prevent data loss scenarios. Several fixes ensure proper context propagation, namespace mapping support, and preflight validation checks that operators depend on for safe restore operations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: in-place restore pre-flight checks, backup queue fixes, CSI volume handle identification, namespace mapping support, and better context propagation in restore operations.

Post for LinkedIn

This week's Velero updates focus on in-place restore reliability and data safety. Key improvements include preflight checks to ensure PVC capacity, fixes to identify volumes by CSI handle instead of PV name, prevention of backup queue deadlocks, namespace mapping support for block data movers, and better error handling in CSI restore operations. These changes strengthen restore workflows for production environments.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.