Skip to content

fix(nvcv): correct header notices for v0.14.1-beta - #300

Merged
dlesage-nvidia merged 3 commits into
release_v0.14.xfrom
v0.14.1-beta
Oct 14, 2026
Merged

dlesage-nvidia merged 3 commits into
release_v0.14.xfrom
v0.14.1-beta

Conversation

@dlesage-nvidia

Copy link
Copy Markdown
Contributor

Summary

Backport the NVCV header-notice correction to the public v0.14.0-beta release, preparing v0.14.1-beta.

This PR targets release_v0.14.x, created at the original v0.14.0-beta commit (d271c1c8788bf697431098b489060e85cf539943), so the backport does not revert changes from newer release lines.

Changes

  • Replace stale proprietary restrictions with standard Apache-2.0 notices in Version.hpp, SymbolVersioning.hpp, and detail/CudaFwd.h; retain the existing Apache-2.0 SPDX license identifiers.
  • Normalize copyright attribution while preserving the original starting years.
  • Add deterministic regression coverage for all three headers.
  • Update CV-CUDA and standalone NVCV to 0.14.1-beta, update the README badge, and add/index the patch-release notes.
  • Preserve the original v0.14.0-beta release notes. Other licensing notices remain outside this backport.

Validation

  • Regression: all three cases fail on the test-only commit and pass after the fix.
  • Header bodies after the opening license comments remain byte-for-byte identical to v0.14.0-beta.
  • C and C++ header syntax checks pass.
  • CPU-only CMake version-header generation passes for CV-CUDA and standalone NVCV: 0.14.1-beta, patch version 1, API code unchanged at 14.
  • Black, Flake8, SPDX, whitespace checks, and release-note parsing/index checks pass.
  • Full CUDA build, GPU tests, and CI results have not been verified.

No release tag or GitHub release is created by this PR.

@dlesage-nvidia
dlesage-nvidia merged commit c53f635 into release_v0.14.x Oct 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants