Conversation
Copilot started reviewing on behalf of
Wassim Chegham (manekinekko)
September 28, 2026 20:27
View session
mnkj0021
force-pushed
the
fix/675-agent-version-build-time
branch
from
September 30, 2026 02:00
1a37198 to
9303727
Compare
mnkj0021
force-pushed
the
fix/675-agent-version-build-time
branch
from
September 30, 2026 03:58
9303727 to
d8ea9b3
Compare
This branch has not been 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.
Fixes #675
Summary
buildTimein the timestamp on the rightRoot cause
The version row displayed
version.createdAton the right while the build metadata displayedversion.buildTime. Those fields can differ, so the UI could show two conflicting dates for the same deployed version.Validation
corepack pnpm --filter portal build— passed on a fresh recheckgit diff --check— passedmain(0 commits behind)GitHub's upstream CI workflows are still in
action_requiredand need a Scope maintainer to approve the fork workflow run. The Microsoft CLA check passes.