update zenodo DOI badge

[Mikejmnez]

This PR adds an updated Zenodo DOI associated with the new release

[coderabbitai]

📝 Walkthrough

Walkthrough

The README Zenodo DOI badge was updated from 10.5281/zenodo.14646648 to 10.5281/zenodo.21540505.

Changes

README DOI update

Layer / File(s)	Summary
Update Zenodo badge reference README.md	The README header now uses the new Zenodo DOI for the badge image and link.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: jgallagher59701

Poem

A rabbit hops past the README line,
“A fresh DOI badge looks divine!”
New Zenodo leaves softly gleam,
Updating the project’s digital dream.
Hop, hop—metadata shines!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is missing the required template sections and most required details.	Add the template sections: Title, Description, Reference ticket, and Tasks checklist, and fill in the ticket and change details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise and accurately summarizes the Zenodo DOI badge update.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update_readme

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jgallagher59701]

Instead of updating the DOI for every release, we would be better off using the 'all versions' DOI, which Zenodo added for things like a README that is not version specific (or at least should not be IMHO). I know that we used to put information in the README about 'this version' but that's pretty tedious to wade through for a 30 year old piece of code.

From Zenodo: "Cite all versions? You can cite all versions by using the DOI 10.5281/zenodo.1013914. This DOI represents all versions, and will always resolve to the latest one. Read more --> https://zenodo.org/help/versioning"

So, I think we should be using the DOI: 10.5281/zenodo.1013914 and not change it for each release. When people cite a certain version, they can use a specific DOI.

Do you agree?