chore(release): prepare v2.0.0

[mmcky]

Prepare v2.0.0

Version bump + CHANGELOG finalization for the 2.0.0 release. No code/behaviour changes.

What's in this PR

• Bump to 2.0.0: package.json + package-lock.json (1.1.1 → 2.0.0), and template.yml (1.0.0 → 2.0.0 — its version had drifted from the package version; now aligned).
• Finalize the CHANGELOG [2.0.0] section (was [Unreleased]), with corrections:
  • Drop the reverted Fix CI: bump @remix-run/* from 1.17 to 1.19 (peer dependency conflict) #29 Remix 1.17→1.19 bump — 2.0.0 stays on the long-standing ~1.17.0 pin (restored at v1.0.1), so there's no net Remix change.
  • Fix the Node floor to >=20 (matching engines).
  • Add the visual-regression harness (test: Playwright visual-regression harness (v1.1.1 baselines) #60) and the three pre-release fixes (fix: wrap page tree in BannerStateProvider (unbreaks @myst-theme 1.x rendering) #61, fix: keep article body in the centered content column #62, fix: pin @remix-run/* to ~1.17.0 to stop the hydration reload loop #63).
  • Restate Security: the older Remix v1 toolchain's npm audit findings remain until the Remix v2 migration (Migrate from Remix v1 to v2 #28).

Why we're ready

2.0.0 is the @myst-theme 0.14 → 1.x upgrade. The three regressions the upgrade introduced are fixed and verified on both the visual-regression fixture and real lecture-wasm content — centered content column, restored "On this page" outline, and no hydration reload loop ("flashing"). None reached users; the 1.x upgrade had never been deployed.

After merge — shipping the release (manual)

Deploy is not automated by merge. From main on Node 24:

make deploy

This builds the bundle and pushes a 🚀 v2.0.0 from <sha> commit to QuantEcon/quantecon-theme. Consumers track that repo's main.zip, so the deploy is the production cutover — render-check a lecture immediately afterwards.

Notes / follow-ups (out of scope here)

• CHANGELOG is dated 2026-06-04, assuming deploy lands today — adjust if it slips.
• Visual-regression baselines are still v1.1.1; re-baseline to 2.0.0 in a fast-follow so the harness guards the new rendering.
• release.yml still runs the Changesets action (harmless now — no changeset files — but conflicts with the decided manual-CHANGELOG + make deploy flow). Clean up as part of Phase 0.
• CHANGELOG compare links are tag-based but the repo has no git tags yet (noted in the CHANGELOG header); introducing tagging is a Phase 0 task.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Prepares the repository metadata for the v2.0.0 release by bumping versions and finalizing the CHANGELOG entry (no runtime/behavior code changes in this PR).

Changes:

• Bump project version to 2.0.0 in package.json, package-lock.json, and template.yml.
• Finalize the CHANGELOG by promoting the prior “Unreleased” v2.0.0 notes into a dated 2.0.0 section, with updated/revised bullet points and links.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
template.yml	Updates template metadata version to 2.0.0.
package.json	Bumps npm package version to 2.0.0.
package-lock.json	Aligns lockfile’s top-level/package entry versions to 2.0.0.
CHANGELOG.md	Finalizes the 2.0.0 release notes and updates the reference link definitions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.