Repository navigation
DOC: refresh README install path and CITATION.cff version - #971
Conversation
|
Thanks for the README and One quick request that we now make of every pull request. QuantEcon has just adopted a Code of AI Use, which welcomes AI-assisted contributions and asks each pull request to say whether AI tools were used. Our pull-request template doesn't show this yet, so we're asking by hand. Could you:
We're asking everyone, so this isn't a flag on your pull request. Thanks! |
QuantEcon#973 added version: 0.12.0 and date-released: 2026-09-24 for the 0.12.0 release, so these lines would have duplicated both keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks @HarshRajSinghania. I pushed one commit (7015864) that drops the CITATION.cff hunk: #973 added |
Summary
Updates identity-facing repo files that had drifted from current install and release practice.
Assisted-by: Grok (Grok 4.6)
Motivation
Closes #900 (remaining acceptance criteria after #941 replaced
copilot-instructions.mdwithAGENTS.md).CITATION.cffhad no softwareversion/date-released, so citation tooling only saw the 2024 JOSS article date.Implementation
CITATION.cffnow has top-levelversion: 0.11.4anddate-released: 2026-07-14(current tagged release). Thepreferred-citationJOSS article block is unchanged.docs/source/contributing.rstdocuments bumping those two fields as part of the release checklist.Testing
__init__.py/ CHANGELOG list0.11.4(14 July 2026) as the current release used for the citation fields.I do not have
cffconvertavailable in this environment. Maintainers can verify with: