Repository navigation
chore: forward-port main into develop (release 2026-10-29, third) - #1198
Merged
Merged
Conversation
…-main release: develop → main (2026-10-29, second)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-main release: develop → main (2026-10-29, third)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Forward-port of main after release #1197 (merge 181a7ac), so develop contains main again.
Carries only main-side commits: the release merge, main's #1193 merge commit, and
render.yaml→ backend imagev2026-10-29b. The only content change against develop is render.yaml. No test.🤖 Generated with Claude Code