fix: yarn.lock repo cleanup and stable test time filter W-23182333#452
Merged
Conversation
nico-pappagianis
approved these changes
Jun 25, 2026
setu4993
approved these changes
Jun 25, 2026
setu4993
changed the title
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
3 participants
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.
What does this PR do?
@salesforce/agents(and its dep graph) against the correct public registry — the lockfile had a bad repo reference that broke installs.'2026-04-07T17:00:00.000Z'--sincevalue withRECENT_MTIME.toISOString(), so the time-filter test stays anchored to the same relative window the fixture data uses (Date.now() - 7d) instead of drifting out of range as the clock moves forward.What issues does this PR fix or reference?
@W-23182333@