Skip to content

[stable33] chore(deps): backport #7633 to stable33#7637

Merged
vitormattos merged 1 commit intostable33from
backport/7633-stable33-lodash-api-extractor
May 5, 2026
Merged

[stable33] chore(deps): backport #7633 to stable33#7637
vitormattos merged 1 commit intostable33from
backport/7633-stable33-lodash-api-extractor

Conversation

@vitormattos
Copy link
Copy Markdown
Member

Backport of #7633 (lodash 4.18.1 and @microsoft/api-extractor 7.58.7 lockfile updates) to stable33.\n\n- Original PR: #7633\n- Method: manual dedicated-clone backport (after /backport command dispatch)

Bumps [lodash](https://github.com/lodash/lodash) and [@microsoft/api-extractor](https://github.com/microsoft/rushstack/tree/HEAD/apps/api-extractor). These dependencies needed to be updated together.

Updates `lodash` from 4.17.23 to 4.18.1
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.23...4.18.1)

Updates `@microsoft/api-extractor` from 7.57.7 to 7.58.7
- [Changelog](https://github.com/microsoft/rushstack/blob/main/apps/api-extractor/CHANGELOG.md)
- [Commits](https://github.com/microsoft/rushstack/commits/@microsoft/api-extractor_v7.58.7/apps/api-extractor)

---
updated-dependencies:
- dependency-name: lodash
  dependency-version: 4.18.1
  dependency-type: indirect
- dependency-name: "@microsoft/api-extractor"
  dependency-version: 7.58.7
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 9129301)
@github-project-automation github-project-automation Bot moved this to 0. Needs triage in Roadmap May 5, 2026
@github-actions github-actions Bot changed the title chore(deps): backport #7633 to stable33 [stable33] chore(deps): backport #7633 to stable33 May 5, 2026
@vitormattos vitormattos merged commit b379025 into stable33 May 5, 2026
62 of 63 checks passed
@vitormattos vitormattos deleted the backport/7633-stable33-lodash-api-extractor branch May 5, 2026 22:18
@github-project-automation github-project-automation Bot moved this from 0. Needs triage to 4. to release in Roadmap May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 4. to release

Development

Successfully merging this pull request may close these issues.

1 participant