Backmerge main into develop (1.16.0) - #897
Merged
Merged
Conversation
Minor release on knowledge bases, marketplace governance, and fine-tuning. - Bedrock Managed Knowledge Base migration lands inert behind nine CDK_MANAGED_KB_* flags (all explicitly false in prod). Adds a Bedrock service role, four Lambdas on one image, a report-only reconciler, four alarms, and the sparse KbWorkIndex GSI. - Marketplace admins can read, test-drive and decline a submission; new terminal 'rejected' listing state. - Fine-tuning wiring restored (FINE_TUNING_ENABLED was never set on the container); access stays whitelist-only at quota 0. Three billing/format bugs fixed. - Live RAG, ungated: queries clamp at 10,000 chars, document-status filter fails CLOSED. - Chat: arrow keys walk the @-mention menu; mentions render as an address. - RBAC: JWT role mappings accept IdP group names containing spaces.
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.
Reconciles
developwithmainafter the 1.16.0 squash-merge (#896).Clean auto-merge — no conflicts. Only the 13 release-artifact files change; no feature code is touched, because
developalready carried all of it.VERSION1.16.0,sync-version.sh --checkPASSCHANGELOG.mdandRELEASE_NOTES.mdboth lead with 1.16.0 above untouched previous entriesgit merge-base --is-ancestor origin/main HEADpassesThe whole point is to make
maina genuine ancestor ofdevelop. Squashing recreates the divergence and the release-artifact conflicts come back next release.(Feature branches into
developsquash as usual — the backmerge is the deliberate exception.)