Increment CalVer to 2026
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6.1k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Since the 2025 Release is still "coming soon" as of 25 December 2025 should we reconsider a late rebrand to 2026?
I suggested this on Slack, reproduced below, when the RC was published too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the 2025 Release status, the linked commit, the referenced Slack discussion, and the current release candidate context first. Done requires a settled decision on whether the release should be rebranded to 2026 and a clearly defined follow-up scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100