[JR-Morgan]

V2 has nulls everywhere

[JR-Morgan]

This change isn't worth deploying on its own, it's v2 edge-cases only.

I'm leaving it parked here waiting for a more critical fix to justify updating the migrator.

[codecov]

Codecov Report

❌ Patch coverage is 10.52632% with 17 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.58%. Comparing base (97666c5) to head (0e70826).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...Sdk.BundleMigrator/Migration/PipelineExtensions.cs	10.52%	11 Missing and 6 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #559      +/-   ##
==========================================
- Coverage   75.59%   75.58%   -0.02%     
==========================================
  Files         483      483              
  Lines       27020    27025       +5     
  Branches     2725     2730       +5     
==========================================
  Hits        20426    20426              
- Misses       5615     5618       +3     
- Partials      979      981       +2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
37689686	Triggered	Generic High Entropy Secret	ad362a6	garage.toml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}