Added#
An issue comes in with a form, labels and a triage state. Three new forms cover what had none:
- a wrong price or a missing model, which asks for the provider's own page, the quote and the day it was read;
- a feature request, which starts with the problem;
- a documentation fault.
Every form, including the two existing ones, starts its issue as
needs-triage. The labels and what each means now live in.github/labels.json, and aLabelsworkflow makes GitHub's list match it using only theghCLI. Until now the only list was GitHub's settings page, and no issue carried a label. CONTRIBUTING.md gains anIssuessection: which form to use, the four triage states, and that an issue is never closed for going quiet. SUPPORT.md links every form.issue-intake.test.jsholds it together:- every label a form or
dependabot.ymlapplies exists; - every label is explained in CONTRIBUTING.md;
- every form is linked from SUPPORT.md;
- every page a form links to exists;
- the workflow never deletes a label.
Eight faults planted one at a time were each caught. The bug form's version hint no longer says there is no npm package. (#665)
A pull request is checked for its issue and for where its changelog line landed. The new
PR readinesscheck, run byscripts/pr-readiness.mjson every pull request, refuses three things:- a description without a closing keyword (
Fixes #<n>); - a line added inside a released version's section of
CHANGELOG.md; - a pull request that adds no line under
Unreleased.
The second is what happened on 2026-11-17: a branch merged
mainafter the 2.7.9 and 2.7.10 releases, git placed its entry inside## 2.7.9without a conflict, andchangelog-coverage.test.js, which can only ask whetherUnreleasedis empty, had nothing to say.Exemptions:
- Dependabot;
- the release pull request, which adds a version heading;
- two labels only a maintainer applies,
no-issueandchangelog-history.
Rebuilt from that merge, the check refuses it. It accepts all 40 of the latest commits on
mainand the 2.7.10 release itself. The description reaches the script through the environment, never inlined into the shell. CONTRIBUTING.md now says how a pull request lands: issue first, squash only, current withmain, and a look at the changelog line after a release. The PR template opens withFixes #..github/rulesets/main-branch.jsonnow allows only squash, requiresPR readiness, and carries thecode_scanningandcode_qualityrules that the ruleset GitHub enforces already had. An admin re-imports it. (#666)- a description without a closing keyword (
Fixed#
Google's prices were re-read, and
gemini-2.5-probills at Gemini 3.8 Flash's rates from 2026-12-01. Google's Gemini API docs moved to aistudio.google.com (the old ai.google.dev pricing address now redirects there), the November review could not reach them, and Google's figures stayed dated 2026-10-10, so the CLI would have warned about every one from 2026-11-25. The pricing, deprecations and caching pages and each row's model page were read on 2026-11-16: every price, cache and batch price, storage price, context window and cache minimum matched, and Google's review date moves. What is new is that "effective December 1, 2026" requests to the retiredgemini-2.5-proroute to Gemini 3.8 Flash and are billed at its rates, $0.75/$3.75 through 2026-12-31 and $1.50/$7.50 after, against $1.25/$10 today. The id now carries both periods, asgrok-4does, and a log spanning the day is billed both ways.gemini-2.5-flashroutes to Gemini 3.5 Flash-Lite that day, whose text rates are the ones it already carries.trazum modelsand the MCPlist_modelstool print a row's current figures, so until 2026-12-01 they show 2.5 Pro at 3.8 Flash's price; a call in a log is priced on its own date. Not changed: the Batch tabs of 3.1 Pro Preview and both 2.5 models charge the standard cache price, and a batch call's cache reads are still billed here at half of it.A release never asked npm about the credential that uploads it. The release job checked the trusted publisher, which refused this workflow at 1.86.0 and refuses it still, and said nothing about the granular token the uploads go through on. That token has an expiry. 2.7.10's release pull request merged on 2026-11-17, the job ran five minutes of checks, and the first upload answered
E404 Not Found - PUT, under a failure note that said of a job holding the token that "this failure is something else". Nothing was half-published, andmainnamed a version npm did not have. Three changes, none of which alters anything installable. The job now asks npmwhoamiwith the stored token beforeverify, on a manual dry run too, so a dry run from a release branch answers before the merge; a refusal is an error on the run page and in the job summary with the steps that fix it, and the failure note asks again and ends on the answer, as does a dry run, in one word. Measured against the live registry: a token npm does not know is answered401, and so was the stored token itself, on a dry run of this change 42 minutes after the failed upload; the token that replaced it was answered200that afternoon, and thirteen minutes later was refused the upload withEOTP, because it had not been made to publish without a one-time code. So the step reports and does not fail, an accepted token is worded as less than a promise, and the failure note namesEOTPbesideE404. The token's expiry date is now recorded in.github/release-credentials.json(nulluntil the owner writes it down), andscripts/freshness.mjscalls it overdue from fourteen days before, which turns the weekly scheduled run red onmain; a date nobody recorded is printed as a note that says so. Andscripts/prepare-release.mjsrefuses to prepare a release once the recorded date has come. The token reaches two more steps ofrelease.ymlthan it did, both running one script of this repository that imports nothing outside Node and sends the token to npm's registry or to nowhere, andsecurity.test.jsholds the list of steps to exactly those. Sixty-one faults planted in the check, the workflow, the date arithmetic and the two scripts that read it were each caught.docs/releasing.mdgains "When the token expires", and loses the paragraph that said there was no token to rotate.