Repository navigation
docs: record the 2026-10-09 upstream follow-up ports - #269
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
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.
The follow-up upstream ports (#266 to #268) weren't in the changelog yet, and what they left out wasn't recorded.
CHANGELOG.md: one outcome line per ported upstream fix under## Unreleased/### Upstream t3code.FUTURE_ENHANCEMENTS.md: what this round left out and why (grouped notifications are mobile only, per-project skill discovery, diff panel all-changes view, compact before send, items that don't apply to the fork, and port limitations).Verified with
vp test run apps/web/src/changelog/parseChangelog.test.ts(15 passed) andvp fmt.🤖 Generated with Claude Code