v68.2.0: roll up post-v68.1.0 master work for publish#231
Merged
Conversation
Consolidates the master-only v68.3.0 (cooldown 15s -> 5s, #229) and v68.4.0 (cold/warm token-fetch instrumentation, #228) CHANGELOG entries into a single v68.2.0 release section, and renumbers the release-pair scripts to v68.2.0/83 to match. GitHub Releases is currently at v68.1.0; the v68.3.0/v68.4.0 labels on master were staging, not formal releases. The next formal published release is v68.2.0, content-identical to the v68.4.0 master snapshot. Auto-update consequence (deliberate): Tampermonkey/Violentmonkey will not downgrade local @Version 68.4.0 to 68.2.0 — clients who pulled the master raw URL between #229's merge and this commit will stay on v68.4.0 (which is a content-superset of v68.2.0) until the next release >=68.5.0 ships. They lose nothing. #230 (IVS WASM crash circuit-breaker, still open) is currently at v68.4.0/85 in its branch and will need rebasing + renumbering (to v68.3.0/84) after this lands. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 21, 2026
ryanbr
added a commit
that referenced
this pull request
May 21, 2026
Roll-up release: converts the current Unreleased work into a dated v68.3.0 section and bumps the release-pair scripts in lockstep (@Version 68.2.0 -> 68.3.0, ourTwitchAdSolutionsVersion 83 -> 84). Only Unreleased item rolling up: PR #232 (ad-spoofing default flipped on -> off). Same publish pattern as PR #226 (v68.0.0) and PR #231 (v68.2.0). The 'field signal' framing in the bullet is also corrected vs the original PR #232 body: the observed symptom was a Twitch ad overlay with countdown reaching the user, not an in-stream ad on the committed backup as I'd wrongly framed in #232. The action (disable by default) still applies — the convergent rationale stands — but the mechanism by which spoofing would drive overlay rendering is honestly noted as unverified. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consolidates the master-only
v68.3.0(cooldown 15s → 5s, #229) andv68.4.0(cold/warm token-fetch instrumentation, #228) CHANGELOG entries into a singlev68.2.0release section, and renumbers the release-pair scripts tov68.2.0/83so the next published release tag matches.Why
GitHub Releases is currently at
v68.1.0; thev68.3.0/v68.4.0labels on master were staging during the multi-PR sequence, not formal releases. The next published release should bev68.2.0, content-equal to the master snapshot at the v68.4.0 squash-merge.Scope of change
CHANGELOG.md: replaces the two separate entries with onev68.2.0section. Performance bullet (cooldown) listed first, Diagnostics bullet (instrumentation) second; companion cross-references updated to reflect the bullets now sit in the same release.vaft/vaft.user.js+vaft/vaft-ublock-origin.js:@version 68.4.0 → 68.2.0,ourTwitchAdSolutionsVersion 85 → 83.CLAUDE.md:Current: vaft 68.2.0/83(Testing651preserved from master).Pure relabeling — no behavioral code change. The cooldown is still 5s; the instrumentation is still active. acorn-clean.
Deliberate auto-update consequence
Tampermonkey/Violentmonkey will not downgrade local
@version 68.4.0 → 68.2.0. Clients who pulled the master raw URL between #228's merge and this commit will stay onv68.4.0until the next release ≥v68.5.0ships. They lose nothing —v68.4.0andv68.2.0are content-equal. Flagging so the maintainer can sanity-check the trade.Knock-on: #230
The IVS WASM crash circuit-breaker PR is currently at
v68.4.0/85in its branch and will need rebasing + renumbering (likely tov68.3.0/84) after this lands. Same reset-and-reapply pattern as the last few rebases. I can take that on once this merges.🤖 Generated with Claude Code