remove warning for element changes

[atravitz]

resolves #1961

Checklist

• All new code is appropriately documented (user-facing code must have complete docstrings).
• Added a news entry, or the changes are not user-facing.
• Ran pre-commit: you can run pre-commit locally or comment on this PR with pre-commit.ci autofix.

Manual Tests: these are slow so don't need to be run every commit, only before merging and when relevant changes are made (generally at reviewer-discretion).

• GPU integration tests
• example notebook testing
• packaging tests: run this for any large feature PRs or PRs that add test data.

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.50%. Comparing base (5347082) to head (9facb94).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1965      +/-   ##
==========================================
- Coverage   94.94%   90.50%   -4.44%     
==========================================
  Files         216      216              
  Lines       20481    20462      -19     
==========================================
- Hits        19445    18520     -925     
- Misses       1036     1942     +906     

Flag	Coverage Δ
fast-tests	90.50% <ø> (?)
slow-tests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.

[hannahbaumann]

Thanks @atravitz , lgtm! I think a news entry would be great for this, but I'll already approve the PR to not block things.

[github-actions]

No API break detected ✅