Skip to content

Revisit db/issue833cleanup#888

Open
dmbates wants to merge 4 commits intomainfrom
db/issue833cleanup
Open

Revisit db/issue833cleanup#888
dmbates wants to merge 4 commits intomainfrom
db/issue833cleanup

Conversation

@dmbates
Copy link
Copy Markdown
Collaborator

@dmbates dmbates commented Apr 23, 2026

I think this is still relevant. These changes only affect an example in the issues directory so I think they can be considered a patch release.

Did behavior change? Did you add need features? If so, please update NEWS.md

  • add entry in NEWS.md
  • after opening this PR, add a reference and run docs/NEWS-update.jl to update the cross-references.

Should we release your changes right away? If so, bump the version:

  • I've bumped the version appropriately

@dmbates dmbates requested a review from palday April 23, 2026 13:40
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.60%. Comparing base (10e6a88) to head (4755a04).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #888   +/-   ##
=======================================
  Coverage   95.60%   95.60%           
=======================================
  Files          38       38           
  Lines        3708     3708           
=======================================
  Hits         3545     3545           
  Misses        163      163           
Flag Coverage Δ
current 95.27% <ø> (ø)
minimum 95.54% <ø> (ø)
nightly 95.27% <ø> (ø)

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.

Copy link
Copy Markdown
Member

@palday palday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no change to the actual package code, so no need to do a release. I agree though that's useful to keep this bit of history around and updated.

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.

2 participants