MAINT: remove end year from copyright

[star1327p]

We don't put the end year in copyright anymore, according to scipy PR 23872 and scipy PR 22300.

[netlify[bot]]

❌ Deploy Preview for scipy-org failed.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d7e7beb69b86eed7ba28efb8caa4462ceeea66b9
🔍 Latest deploy log	https://app.netlify.com/projects/scipy-org/deploys/68ffc959944e4f00077756df

[lucascolley]

@tylerjereddy any idea what's up with netlify?

[tylerjereddy]

I'm not sure, the first failure in the log involves type stubs (below). Must be @jorenham's fault (I'm kidding--I'm not sure what is going on).

1:35:28 PM:   ✖ FAIL fragment-check public/ja/install/index.html --> /ja/install/#type-stubs
1:35:28 PM:   | operator: fragment-check
1:35:28 PM:   | expected: id="type-stubs"
1:35:28 PM:   |       at: public/ja/install/index.html:166:10 <a href="/ja/install/#type-stubs">...</a>

The log does have a ton of Dart Sass: DEPRECATED, but might just be a red herring. Maybe we need to compare a recent succeeding log with this new failing one.

Seems hard to image the diff here could be causing the problem.

[jorenham]

Must be @jorenham's fault (I'm kidding--I'm not sure what is going on).

I usually blame mypy in situations like these 😛. But in these case, seeing as there's also another similar error, maybe we could just blame pip instead:

8:35:28 PM:   ✖ FAIL fragment-check public/ja/beginner-install/index.html --> /ja/install/#installing-with-pip
8:35:28 PM:   | operator: fragment-check
8:35:28 PM:   | expected: id="installing-with-pip"
8:35:28 PM:   |       at: public/ja/beginner-install/index.html:196:127 <a href="/ja/install/#installing-with-pip">...</a>

Anyway, jokes aside, I have some wild guesses:

These errors "feel" more like warnings to me, so maybe there's a CI config that causes warnings to be reported as errors, like in https://answers.netlify.com/t/build-script-returned-non-zero-exit-code-2-appears-when-i-try-to-deploy-site/101436/2 ?

Or, seeing as this is failing for the Japanese docs; maybe there's a i18n/l10n issue that's causing mismatches between id="..." and the fragment names?