Skip to content

Conversation

@jeremymeng
Copy link
Owner

No description provided.

azure-sdk and others added 21 commits November 17, 2025 08:55
This is an automatic PR generated weekly with changes from running the
command pnpm update
Upgrade typescript-eslint related dev dependencies to ~8.46.4 following
the same approach as PR #35869.

## Changes Made

- **common/tools/dev-tool/package.json**: Upgraded `typescript-eslint`
from ~8.43.0 to ~8.46.4
- **common/tools/eslint-plugin-azure-sdk/package.json**: Upgraded all
@typescript-eslint packages from ~8.43.0 to ~8.46.4
- **common/tools/vite-plugin-browser-test-map/package.json**: Upgraded
`typescript-eslint` from ~8.43.0 to ~8.46.4
- **eng/containers/turborepo-remote-cache/package.json**: Upgraded
`typescript-eslint` from ~8.43.0 to ~8.46.4
- **sdk/monitor/monitor-opentelemetry/samples-dev/package.json**:
Upgraded @typescript-eslint packages from ^8.38.0 to ~8.46.4
(auto-updated by pnpm)
- **pnpm-lock.yaml**: Updated with new dependency versions
In build pipelines there are intermittent failure in vitest browser
testing even before any tests. They usually pass after re-run.

> [vitest] Error: listen EACCES: permission denied ::1:63315

It's possible that app or service is using 63315 port as 49152–65535 is
the IANA-designated dynamic/ephemeral port range.

This PR attempts to improve the test reliability by using port lower
port number of 43315.

### Packages impacted by this PR
N/A
- if running live tests. because in some packages due to recorder
limitation, not all tests are enabled for playback so code coverage data
for playback tests are not accurate.
- or running azure core tests. because they don't have live tests.
### Packages impacted by this PR

- `@azure/eslint-plugin-azure-sdk`

### Issues associated with this PR

Resolves issue requesting upgrade of `@eslint/compat` from 1.4.1 to
2.0.0

### Describe the problem that is addressed by this PR

The `@eslint/compat` package has a new version (2.0.0) available. The
package is used exclusively in `common/tools/eslint-plugin-azure-sdk`
for the `fixupPluginRules` function and type definitions.

### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?

Direct dependency version update. Breaking change is Node.js version
requirement (`^20.19.0 || ^22.13.0 || >=24`), already satisfied. API
surface unchanged—no code modifications required.

### Are there test cases added in this PR? _(If not, why?)_

No. Existing 659 tests verify compatibility. No functional changes to
test.

### Provide a list of related PRs _(if any)_

N/A

### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

N/A

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)

<!-- START COPILOT CODING AGENT SUFFIX -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Dependency package @eslint/compat has a new version
available</issue_title>
> <issue_description>We have identified a dependency on version 1.4.1 of
[@eslint/compat](https://www.npmjs.com/package/@eslint/compat). A new
version (2.0.0) is available for upgrade.
> 
> Following are the steps to upgrade package dependency.
> 
> 1. Understand the breaking changes between the version being used and
the version you want to upgrade to.
> 
>   2. Identify all packages that take a dependency on this package.
> 
> 3. Go to the root folder for each such package
(/sdk/service-name/package-name) and update package.json to have the new
version.
> 
>   4. Run 'pnpm install' to ensure the new version is pulled in.
> 
>   5. Make relevant changes to absorb the breaking changes.
> 
> 6. Repeat steps 3 to 5 for each of the packages that have a dependency
on this package.</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>

- Fixes #36619

<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in
our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: jeremymeng <[email protected]>
Post release automated changes for azure-data-tables
### Packages impacted by this PR


### Issues associated with this PR


### Describe the problem that is addressed by this PR


### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_


### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR


### Issues associated with this PR


### Describe the problem that is addressed by this PR


### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?


### Are there test cases added in this PR? _(If not, why?)_


### Provide a list of related PRs _(if any)_


### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
Sync eng/common directory with azure-sdk-tools for PR
Azure/azure-sdk-tools#12911 See [eng/common
workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@jeremymeng jeremymeng merged commit 44fcec0 into jeremymeng:test-custom-agents Nov 18, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants