Skip to content

Sync eng/common directory with azure-sdk-tools for PR 11365 #42244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 29, 2025

Conversation

azure-sdk
Copy link
Collaborator

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#11365 See eng/common workflow

@azure-sdk azure-sdk requested review from Copilot and weshaggard and removed request for weshaggard July 28, 2025 17:32
@azure-sdk azure-sdk added the EngSys This issue is impacting the engineering system. label Jul 28, 2025
@azure-sdk azure-sdk requested a review from a team as a code owner July 28, 2025 17:32
@azure-sdk azure-sdk added the Central-EngSys This issue is owned by the Engineering System team. label Jul 28, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR synchronizes the eng/common directory with azure-sdk-tools repository to incorporate changes from PR 11365. The change addresses error handling in the npm publishing pipeline by resetting the global exit code after a warning.

Key Changes

  • Resets the global LASTEXITCODE to 0 after handling a non-critical npm view failure

@azure-sdk azure-sdk merged commit 1b0d6f8 into main Jul 29, 2025
21 checks passed
@azure-sdk azure-sdk deleted the sync-eng/common-weshaggard-patch-1-11365 branch July 29, 2025 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants