Skip to content

[pull] main from microsoft:main#1321

Merged
pull[bot] merged 16 commits into
code:mainfrom
microsoft:main
Jun 1, 2026
Merged

[pull] main from microsoft:main#1321
pull[bot] merged 16 commits into
code:mainfrom
microsoft:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Jun 1, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

vs-code-engineering Bot and others added 16 commits June 1, 2026 15:38
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…cards

Render chat attachments as request tiles
* theme: add selection border for menu items in light and dark themes

Co-authored-by: Copilot <copilot@github.com>

* theme: improve specificity for high contrast menu selection border

Co-authored-by: Copilot <copilot@github.com>

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
[chat-lib] Preserve target document URI on NES results

The NES facade exposed in chat-lib was dropping the target document id
when constructing the public NESResult, so cross-file Next Edit
Suggestions could not be routed to the correct document downstream
(notably the Copilot Language Server / Visual Studio).

This forwards `targetDocumentId.uri` from the internal next-edit result
as an optional `targetDocumentUri` on `INESResult.result`. When the
field is omitted, consumers continue to apply the edit to the requested
document, preserving backward compatibility for single-file callers.

Refs microsoft/vscode-internalbacklog#7835

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fix icon color clash on selected rows in focused session list

Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
)

* Initial plan

* [bat] Make folding markers case-insensitive for REM

Co-authored-by: aeschli <6461412+aeschli@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: aeschli <6461412+aeschli@users.noreply.github.com>
Local sessions can now host multiple chats. The parent->child hierarchy is
stored entirely in the provider's own IStorageService metadata via a new
`parentUri` field on the stored session, so it survives reloads with no
extra dependencies.

- getSessions() surfaces only primary chats; children are aggregated into
  their primary's group via a cached, live ISession whose `chats` observable
  re-derives on membership changes and whose status/updatedAt/isRead/
  lastTurnEnd are aggregated across the group.
- createNewChat(sessionId) on a committed session creates a linked child;
  sendRequest routes follow-ups (group id + child resource) to the child.
  A rejected/unsent child is rolled back and never persisted.
- deleteChat removes a single child; deleting the primary (or last chat)
  tears down the whole group. On load, an orphaned child (missing parent)
  is promoted to a primary.
- Multi-chat is always on (no setting).

Adds 10 unit tests covering grouping, persistence/restore, orphan
promotion, child/primary deletion, rejected-send rollback, and group
status aggregation. Updates LOCAL_CHAT_SESSIONS_PROVIDER.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
…lbar (#319337)

Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
* Bump version to 1.124.0

* Revert distro change to match main

The distro field was carried over from before PR #319280 reverted it on main.
Removing the distro change so the bump PR only modifies version-related fields,
matching the workflow's PKG_LOCK_AND_COPILOT exception.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Ulugbek Abdullaev <uabdullaev@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* extensions: delay auto-update of new versions by 2 hours

Revert the `extensions.autoUpdate` setting back to its original form
(boolean enum, no policy, no 'delayed' value) and instead always delay
auto-updating an extension until 2 hours after a new version has been
published. Manual updates still update immediately.

- New versions are auto updated 2 hours after they are published
- Manual updates are unaffected
- While delayed, the extension is shown as outdated with an info status
  explaining when it will be auto updated; the activity badge is not shown
- Migrate the insiders 'on' | 'delayed' | 'off' values of
  extensions.autoUpdate back to booleans (on/delayed -> true, off -> false),
  with a runtime fallback in getAutoUpdateValue
- Remove the ExtensionsAutoUpdate policy entry from policyData.jsonc

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* extensions: address review feedback for delayed auto-update

- Declare type: ['boolean', 'string'] on the extensions.autoUpdate schema
- Show the Update All Extensions title action whenever there are outdated
  extensions (rely on HasOutdatedExtensionsContext), so it stays
  discoverable in the default auto-update mode now that updates are delayed
- Make getAutoUpdateValue type-safe by widening the getValue generic and
  dropping the any casts / eslint-disable comments
- Gate the plugin daily update check on getAutoUpdateValue() === true to
  match PluginAutoUpdate and avoid needless network fetches
- Exercise an unsigned gallery extension in the signing-agnostic delay test
- Add a regression test for getAutoUpdateValue legacy value normalization

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pull pull Bot locked and limited conversation to collaborators Jun 1, 2026
@pull pull Bot added the ⤵️ pull label Jun 1, 2026
@pull pull Bot merged commit 57aca5e into code:main Jun 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants