There's some behavior change that adds parentheses for nullish coalescing in
ternary. So we will need to re-format our code base.
- remove prettier from packages that don't need them since we run the vendored
version via dev-tool
It helps old JS runtimes that only support ES 5 but we moved to ES 6
long time ago
and now moved to ES2017. Most of our packages don't have this option.
This PR
removes its usage.
### Packages impacted by this PR
@azure/-tools/vite-plugin-browser-test-map
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
The type declaration file wasn't set in package.json and the return type
of the plugin function was too permissive causing type errors when
imported.
### 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?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)
### Packages impacted by this PR
@azure/monitor-opentelemetry
### Describe the problem that is addressed by this PR
Updates the @microsoft/applicationinsights-web-snippet package to the
latest version.
### 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)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
1. @azure/eventgrid-namespaces
2. @azure/eventgrid
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/29699
### Describe the problem that is addressed by this PR
This PR has been created to move the eventgrid packages away from Local
Authentication. The migration guide has been used for reference.
### 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?
No special design consideration.
### Are there test cases added in this PR? _(If not, why?)_
NA. Existing test cases are sufficient.
### Provide a list of related PRs _(if any)_
1. https://github.com/Azure/azure-sdk-for-js/issues/29699
2. https://github.com/Azure/azure-sdk-for-js/pull/30209
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)
Update tsp-location.yaml to point to a commit from main in the spec repo
and regenerate. The previous commit hash was from a branch never merged,
blocking the attempt to release the sdk
After regenerating from latest tsp main, those were the changes
introduced:
* EnvionmentType name was updated to readonly (later fix added on the
typespec)
* PollingHelper and lro packages got updated (updated by code gen). Live
test for the LRO operations was executed and no issue was detected.
Previous PR for current sdk:
https://github.com/Azure/azure-sdk-for-js/pull/29512
APIView: [@azure-rest/developer-devcenter -
apiview.dev](https://apiview.dev/Assemblies/Review/e17096012eb7466a8aab7c74742c6bff?revisionId=b4d2f5f84d98499dacfcc5e7cdd15d52)
---------
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
Previously it was checking the existence of .tshy directory. Now that we
removed
all .tshy the code is broken. This PR updates to check the package.json
instead.
### 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
@azure/ai-inference
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Initial release of @azure/ai-inference SDK
### 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
- @azure/dev-tool
### Issues associated with this PR
- #30160
### Describe the problem that is addressed by this PR
Updates to latest ts-morph package.
### 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
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds the following:
- Global regex replace for context replacements
- Changes sinon spy to `vi.spyOn`
- Adds node specifiers to node imports
### 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
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Fixed the `beforeEach` statements to get rid of the Mocha `Context` and
replace with `vitest` context and fixes the test-recorder creation.
### 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)
to fix broken nightly pipelines where we update `@azure` package
versions to
nightly versions and dependency versions to a range for their nightly
versions.
Versino `^3.0.0` would not get updated because of the following chech in
`set-dev.js` then `rush install` would fail to find matching one and
report error.
9488fe4bd7/eng/tools/versioning/set-dev.js (L80)
### Packages impacted by this PR
@azure-tools/test-credentials
### Issues associated with this PR
### Describe the problem that is addressed by this PR
- Exclude Managed Identity from DAC so that we can run live test
pipeline successfully. The 4 credentials that we try is: Powershell,
Cli, Developer Cli, Environment Credential in listed order. See [the migration
guide](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1080/Secret-auth-migration)
- Increase the default timeout for vitest to our default timeout (18000
ms)
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds updates for the following:
- Changes assert to only use `vitest` for now and not sure the
`@azure-tools/test-utils`
- Any utility in the `/test` folders will be updated to use `vitest` for
assertions
- Add `beforeEach`, `afterEach`, `vi` and `expect` to any test class
using `sinon` for easy replacement
- Fix pathing issue so that `import { foo } from "..";` is translated to
`import { foo } from "../index.js";`
- Removes `source-map-support` as we're not using Karma.
### 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
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Creates a starter migration toolkit for projects to move to ESM and
vitest. This project for dev-tool introduces a tool invoked such as the
following to migrate service-bus
```
dev-tool admin migrate-package --package-name=@azure/service-bus
```
This does the following:
- Changes the package.json for the following:
- Removes chai/mocha/karma
- Adds vitest and tshy
- Modifies the build and test commands
- Renames the mapped files to the proper output type such as
`-browser.mts`
- Changes the tsconfig.json for the following:
- Moves module and moduleResolution to NodeNext
- Removes outDir and declarationDir
- Fixes the source files
- Uses extension for files such as "foo.js" instead of "foo"
- Removes "chai" usage
- Adds vitest usage for spec files
- Fixes api-extractor.json
- Fixes input path for source
- Fixes output trimmed path
- Migrate Testing
- Writes for both browser and node unit tests
- Writes config for building browser bundle
- Removes .nycrc and Karma configuration
### 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)
Sample source structure used to be flat but later nested directories are
supported as well. This PR fix the glob pattern to also include sub
directories.
- also re-publish samples for @azure/service-bus
I didn't update all the other samples as there are no complaints. They
can get new update in their next publish.
### Packages impacted by this PR
@Azure/communication-chat
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Customer escalated the issue:
The issue was introduced from the @azure/communication-chat@1.4.0. Chat
client updated the internal API client by generating the new service
client version with the `endpoint` param to replace the `baseUri` and
kept the dependency version @azure/core-client@1.3.0 and higher. While
the `endpoint` is introduced only in @azure/core-client@1.6.0.
Customer see error "baseUrl is not specified" if the dependency version
not updated.
Update the @azure/core-client version to fix the issue
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)_
- [x] 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)
### Packages impacted by this PR
- @azure/monitor-opentelemetry
- @azure/monitor-opentelemetry-exporter
- @azure/opentelemetry-instrumentation-azure-sdk
### Issues associated with this PR
- #29972
- #29971
- #29970
- #29969
- #29968
- #29967
- #29966
- #29965
- #29964
- #29963
- #29962
### 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)
---------
Co-authored-by: Jackson Weber <jacksonweber@microsoft.com>
### Packages impacted by this PR
@azure/eventgrid-system-events
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
1. Originally, there was one unified package -
[`@azure/eventgrid`](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventgrid/eventgrid).
This package was generated from Swagger specification.
2. Earlier in April 2024, some parts of the `@azure/eventgrid` package
were extracted out to create a new package -
[`@azure/eventgrid-namespaces`](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventgrid/eventgrid-namespaces).
This package was generated from Typespec specification.
3. Now, with this PR, we are looking at the second split of the
`@azure/eventgrid` package. All System Events have been extracted out of
the swagger specification to Typespec specification. This is a new
package named `@azure/eventgrid-system-events`.
### 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?
1. In the Typespec core generator, We have an issue where client name
overrides are not applied to `alias`. I have created an issue
https://github.com/microsoft/typespec/issues/3240 to fix this. In the
meantime, I have handled this issue in the custom code.
2. With the new generator, `Known*` models are not generated. I have
created an issue
https://github.com/Azure/autorest.typescript/issues/2476 to fix this. In
the meantime, I have handled this issue in the custom code.
3. In the previous generator, we had several properties which were
overridden as mandatory parameters. With the new generator, such mass
overrides are not possible. So, we are allowing them to be optional and
close to the Wore specification. This is in parity with the other
language SDKs.
### Are there test cases added in this PR? _(If not, why?)_
No. They are all model objects. No code functionality is involved.
### Provide a list of related PRs _(if any)_
1. https://github.com/microsoft/typespec/issues/3240
2. https://github.com/Azure/autorest.typescript/issues/2476
3. https://github.com/Azure/azure-sdk-for-js/pull/29245
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`npx tsp compile client.tsp`
### Checklists
- [X] Added impacted package name to the issue description
- [X] 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)_
- [X] Added a changelog (if necessary)
@xirzec @joheredi @lmazuel FYI......
---------
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
as packages using tshy has been migrated to ESM and these rules no
longer apply to them.
This PR skip these rules to avoid having to turn them off for individual
packages.
### 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?
We could remove these rules too. Although it's still nice to have them
before we migrage all packages to ESM with tshy.
### Packages impacted by this PR
@azure/core-amqp, @azure/event-hubs, and
@azure/eventhubs-checkpointstore-blob
### Issues associated with this PR
Gist: https://gist.github.com/conniey/f96d64547efa955a9e763cee6b65d1fc
### Describe the problem that is addressed by this PR
Enable the SDK to communicate with GeoDR-enabled Event Hubs.
### 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?
The PR follows closely what the crew agreed on for now which is changing
the type of `offset`s to be a string but this will be revisited later.
### Are there test cases added in this PR? _(If not, why?)_
Tests will come later.
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Creates a list tool to track our migration to ESM efforts.
### 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)
In an ESLint configuration object, if an `ignores` key is used without any other
keys, then the patterns act as global ignores. I added a `name` in my previous
PR which broke it.
This PR fixes the issue by removing the extraneous name. A pattern of
`*.config.{js,cjs,mjs}` is also add to global ignores because we don't need to
lint them.
Also in this PR
- move app-configuration package to use Flat Config format as a test.
- enable cosmosdb test config that was in legacy config format but missed in migration.
### Packages impacted by this PR
- @azure/web-pubsub-express
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Updates to ESM via `tshy` and moves from Mocha/Chai/Sinon to `vitest`
### 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)
This reverts commit 11da215483.
Unfortunately, rush does not play well with peerDeps and I am bumping
into https://github.com/microsoft/rushstack/issues/1415
I really wanted this to work but rather than continue going down this
path I think it's safer to revert and find an alternative
given the issues with rush and pnpm
### Packages impacted by this PR
dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
We run into preflight CORS issue while testing App Config migration to
DAC in the browser. This PR update the relay server to allow
"Content-Type" and other headers to mitigate the issue.
### 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?
The other solution is to use `cors` middleware package to ensure the
preflight request succeeds.
Updates @azure-tools/test-utils to 1.0.2 since 1.0.1 has been published
to NPM already.
Also, run rush update --full to ensure everyone is on the repo-source
version of test-utils until we can fix the NPM version.
### 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
@azure-tools/test-utils
### Issues associated with this PR
Resolves#29736
### Describe the problem that is addressed by this PR
When @azure-tools/test-utils moves to `npm` it will no longer default to
the on-disk version of core-tracing. This impacts our `supportsTracing`
test helper as it no longer sets the instrumenter on the same version as
the client package. Imagine this flow:
<img
src="https://github.com/Azure/azure-sdk-for-js/assets/753570/12d52e8e-16c1-44b3-b57d-edd31a1e4627"
width=70% height=70%>
In this case, test-util and app-configuration are not talking to the
same "module global" instrumenter.
This PR fixes this by removing core-tracing from test-utils, setting it
as a peerDependency instead. All packages that test tracing also
implement tracing, and as such are already depending on core-tracing.
This was verified locally, but I'll need to get it out to NPM before
verification can complete
### Alternatives
See #29709 for a few alternatives:
1. Pass the instrumenter through
2. Use mocks
Both require updates to multiple packages and/or adding public API
surface which is unnecessary. We can fallback to those options if we
have to, but this is a promising alternative.
### Packages impacted by this PR
@azure-rest/ai-vision-face
### Issues associated with this PR
### Describe the problem that is addressed by this PR
1. tsp-client update to
60161e2f7d
([commit](2189b834bb))
- Ref: history of face spec
https://github.com/Azure/azure-rest-api-specs/commits/main/specification/ai/Face
2. Refine customization to not set MFD filename when there has already
been one.
([commit](d688279d32))
3. Use the `extraFiles` config to copy sample images.
([commit](389b01dc87))
4. Fix sanitizer issues in tests.
([commit](3354597f01))
5. Update the core-lro to v3 preview version.
([commit](7ac973d218))
- Cherry-picked from
56d85526df
6. tsp-client update to
1d2253d1e2
([commit](9e3a10a519))
### 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)
---------
Co-authored-by: Chung Sheng Fu <Chung.Fu@microsoft.com>
To do:
[x] Regenerate from merged tsp spec
[x] Update tests to use vitest
[x] Record tests
[x] Update samples
[] ~~Update Readme~~
[x] Update Changelog
[x] Update LRO status model fixed in tsp latest api version pr
---------
Co-authored-by: Lei Tian <leti@microsoft.com>
### Packages impacted by this PR
- @azure/core-amqp
### Issues associated with this PR
- #29683
### Describe the problem that is addressed by this PR
Removes esbuild and its polyfills for Node in favor of vite and vite
node plugins.
### 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)
ESLint v9 drops support for legacy .eslintrc style configuration files.
To move to v9 we need to migrate to the new Flat Config files. This PR
adds support for Flat Config file and migrate cosmos and identity-broker
packages to use the flat config. Legacy config files are still
supported.
Some eslint plugins that we use don't support flat config yet so they
are disabled.
Related issue: https://github.com/Azure/azure-sdk-for-js/issues/29750
The breaking change that impacts us is that now `typescript` and `javascript` code blocks in markdown files are maped to virtual files with `.ts` or `.js`, instead of `.typescript` or `.javascript` as previously in v4.
This PR reacts to the change:
- Add an overrides entry for `**/*.md/*.ts` because they now match the files pattern of our first overrides entry. Previously they are not linted because of their old `.typescript` extension. Their `project` is set to `null` as they don't belong to any project. They still are benefited from rules that don't require type checking.
## What's happening?
- [x] Get Scott's test-proxy version from #29471
- [x] Update `recorder 3.5.0` with
- [x] Central Sanitizers
- [x] /removeSanitizers API
- [x] remove fallback sanitizers
- [x] Publish `recorder 3.5.0`
- [x] Update `recorder 4.x` with the `recorder 3.5.0` changes and make
sure they are in sync.
- [x] Update lock file with `rush update --full` to get latest recorder
and test-credential packages
- [x] Test/fix packages
- [x] recorder
- [x] storage
- [x] template
- [x] '@azure-rest/synapse-access-control'
- [x] '@azure/arm-resources'
- [x] arm-links
- [x] arm-resources
- [x] event-grid
- [x] template-dpg
- [x] synpase packages
- [ ] '@azure/identity' (future PR)
- [x] '@azure/arm-eventgrid'
- [x] '@azure/ai-text-analytics'
## Future Work
- [ ] Figure out identity tests/recordings
- [ ] Make sure CI pipelines for each of the services that are not
triggered in this PR get to green by either re-recording or tweaking the
recorder config for the package
---------
Co-authored-by: Scott Beddall (from Dev Box) <scbedd@microsoft.com>
### Packages impacted by this PR
@azure-rest/ai-vision-face
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Generate and implement Face SDK via TypeSpec.
### 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)
---------
Co-authored-by: SDKAuto <sdkautomation@microsoft.com>
Co-authored-by: Chung Sheng Fu <Chung.Fu@microsoft.com>
### Packages impacted by this PR
- `@azure-tools/dev-tool`
- `@azure-tools/test-credential`
### Describe the problem that is addressed by this PR
We want to move to user auth and `DefaultAzureCredential` to
authenticate our tests, but `DefaultAzureCredential` does not work in
the browser, blocking this transition.
This PR proposes a solution -- create a short-lived, local-only, server
which can create tokens in Node using DefaultAzureCredential. In the
browser, createTestCredential provides a credential implementation which
calls this server whenever it needs a token, and the server relays the
request to DefaultAzureCredential.
Here's what's changed:
- `test-credential` now returns a credential which requests tokens from
a local web endpoint when running browser tests against a live service.
- `dev-tool` contains an implementation of this web endpoint. The
dev-tool scripts used to run browser tests now start this server
automatically when running browser tests. A separate command to start
the server is also provided for pipelines.
- Update live test pipelines to start the server when running browser
tests.
### Provide a list of related PRs _(if any)_
- Draft version with loads of commits and `/azp run` spam: #29581
- Harsha's earlier PR to enable DefaultAzureCredential:
https://github.com/Azure/azure-sdk-for-js/pull/29577
### Packages impacted by this PR
`@azure-tools/test-credential`
### Describe the problem that is addressed by this PR
Need to move away from client secrets in the dev workflow.
### Breaking Changes
Updates the `createTestCredential` method to consume
`DefaultAzureCredential` instead of `ClientSecretCredential` in order to
offer autonomy to the devs and to move away from clietn secrets in
environment varaibles.
- `NoOpCredential` is offered for playback and `DefaultAzureCredential`
in record/live modes.
- [`User Auth` and `Auth via development
tools`](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/identity/identity#authenticate-users)
are preferred in record mode to record the tests.
### TO DO
Hotfix 1.x release with the same change.
---------
Co-authored-by: Timo van Veenendaal <me@timo.nz>
### Packages impacted by this PR
- @azure/core-amqp
### Describe the problem that is addressed by this PR
Moves `@azure/core-amqp` to ESM via `tshy` and unit tests from `mocha`
to `vitest`.
---------
Co-authored-by: Jeff Fisher <jeffish@microsoft.com>
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
- fix false positive when there are no comments at all. There may be
some internal cache nodes in the array but they don't hold any comments.
- instead of showing squiggles for whole declaration body, only report
on the id node if its available.
### Packages impacted by this PR
- @azure/template
### Issues associated with this PR
- #29538
### Describe the problem that is addressed by this PR
Adding `loupe` directly to `template` and removing from `test-recorder`.
### 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
`@azure/eslint-plugin-azure-sdk`
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/22698https://github.com/Azure/azure-sdk-for-js/issues/22699https://github.com/Azure/azure-sdk-for-js/issues/22700https://github.com/Azure/azure-sdk-for-js/issues/22701
### Describe the problem that is addressed by this PR
This moves us from v5 -> v6 of eslint-typescript dependencies. The
current stable is 7 with 8 in early alpha. Since major changes include
breaks, it was easier to do this migration one major version at a time,
hence starting with the upgrade to 6. I am hopeful that 6 -> 7 will be
less messy, but I make no promises.
The major annoyance I ran into is you have to create mock "fixtures"
(dummy files) for any test asset paths (e.g. you tell the linter you are
testing `foo/bar/baz.ts` you need a tsconfig somewhere with that file
listed as included *and* you need that exact directory/file structure on
disk somewhere. eslint-typescript blames typescript for this limitation,
but I'm not familiar enough with the parser APIs to know if they're
correct in their analysis.
Note: I haven't gone through to audit all the rules yet, as some are
still a bit busted or need to be removed, but for the sake of updating
our dependencies, I moved everything forward as-is.
### Packages impacted by this PR
- @azure/opentelemetry-instrumentation-azure-sdk
- @azure/monitor-opentelemetry
- @azure/monitor-opentelemetry-exporter
- @azure/monitor-query
### Issues associated with this PR
- #29486
- #29487
- #29488
- #29489
- #29490
- #29491
- #29492
- #29493
- #29494
- #29495
- #29496
- #29497
### 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
- [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)
### Packages impacted by this PR
- @azure/dev-tool
- @azure/eslint-plugin-azure-sdk
### Issues associated with this PR
- #29502
### Describe the problem that is addressed by this PR
Moves the `vitest` to use `.mts` for the config to opt in to ESM builds
for `vite`.
### 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?
Updated as per recommendation here
https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated
### 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
- [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)
### Packages impacted by this PR
- @azure/api-management-custom-widgets-scaffolder
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/22972
- #24124
- https://github.com/Azure/azure-sdk-for-js/issues/25509
### Describe the problem that is addressed by this PR
Updates `inquirer` which uses ESM only, so this moves to ESM, but also
allows for CJS.
### 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
- [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)
---------
Co-authored-by: Jeff Fisher <jeffish@microsoft.com>
* allow an override FILE to be honored by test-proxy-tool
* update test-utils to honor proxy override version by default
---------
Co-authored-by: Scott Beddall (from Dev Box) <scbedd@microsoft.com>
### Packages impacted by this PR
- `@azure/core-client-rest`
### Issues associated with this PR
- Resolves#28971
### Describe the problem that is addressed by this PR
- Major bump of `@azure-rest/core-client` to 2.0.0 due to introduced
behavioral breaking change.
- The expected body shape for `multipart/form-data` is now an array of
`PartDescriptor`, which has the following fields:
- `headers` and `body` representing the multipart request headers and
body
- Convenience fields for MIME header values:
- `contentType`, for the `Content-Type` MIME header
- `name`, `filename`, `dispositionType`, for constructing the
`Content-Disposition` MIME header
- These convenience values take precedence over any existing MIME
information (name and filename) present in the request body (i.e. the
`name` property on `File` and the `type` property on both `File` and
`Blob`)
- If the headers are set explicitly in the `headers` bag, the headers
bag value takes precedence above all.
- Implemented part serialization flowchart more or less as described in
the Loop, with a couple of notable differences (and other less notable
ones):
- `string` values are put directly on the wire regardless of content
type; this allows for customers to pass pre-serialized JSON to the
service
- If no content type is specified, and we cannot infer the content type,
we default to `application/json` (i.e. there is no situation where we
would throw a "cannot encode type" error)
- Added support for `FormData` objects. If a `FormData` object is
encountered, it is passed directly to `core-rest-pipeline` for it to
handle.
### Are there test cases added in this PR? _(If not, why?)_
Yes
### To do
- [ ] Port Core change to ts-http-runtime before merging
This PR extends dev-tool's `admin list packages` to optionally run
custom tasks on each package in the list.
For example,
`npx dev-tool admin list packages --task=/path/to/echo-packages.js` with
a echo-package.js of
```js
const path = require("path");
export default async function EchoPackage(project, paths, cwd, root) {
console.dir({
project,
paths,
cwd,
root,
});
}
```
would output items like
```
{
project: {
packageName: '@azure/arm-springappdiscovery',
projectFolder: 'sdk/springappdiscovery/arm-springappdiscovery',
versionPolicyName: 'management'
},
paths: false,
cwd: '/home/meng/git/jsmain/sdk/tables/data-tables',
root: '/home/meng/git/jsmain'
}
```
while
`npx dev-tool admin list packages
--task=/home/meng/git/jsmain/common/tools/dev-tool/src/commands/admin/list/tasks/update-package.ts`
would perform updates on projects whose package.json satisfies some
condition.
I had to downgrade `strip-json-comments` because v5 is pure ESM which
broke the
`admin list` command.
Updating the recorder to the latest v3.2.0 to consume the latest central
sanitizers through `rush update -full`
Skipping the following unit test pipelines with failures
- storage-file-share (browser unit tests only)
- storage-file-datalake
- text analytics
- ai-language-text
- ai-language-conversations
This is expected and is needed for the spring grove efforts.
Issue to track unskipping
https://github.com/Azure/azure-sdk-for-js/issues/29367
### Packages impacted by this PR
All via dev-tool
### Issues associated with this PR
Contributes to #28617
### Describe the problem that is addressed by this PR
esm is still being required in our test:node-ts-input and I don't
believe it is necessary. I'm removing it, but PLEASE do let me know what I'm missing -
I don't know much about mocha config to be honest.
### Packages impacted by this PR
@azure/core-client
@azure/core-tracing
@azure/template
### Issues associated with this PR
Resolves#28820
### Describe the problem that is addressed by this PR
This PR:
- Updates extract-api to work with both tshy aware packages and subpath
export packages
- Migrates core-client, core-tracing, and template to the extract-api
script
### Packages impacted by this PR
`@azure/template`
### Issues associated with this PR
`@azure/template` being upgraded
- commonJS to esm
- mocha/karma to vite/playwright
- recorder v3 to recorder v4
- test-credential v1 to v2
This would also serve as an example for future migrations.
---------
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
We no longer use esm4mocha, instead relying on tsx for our node-js-input
tests.
Now that this has been in place for some time, we can remove esm4mocha
followed by the esm dependency.
Contributes to #28617
### Packages impacted by this PR
- @azure/notification-hubs
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Moves the `@azure/notification-hubs` to `vitest` with different configs
for browser, and node.js with different configs for unit tests versus
integration tests.
### 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
- [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)
### Packages impacted by this PR
@azure/eventgrid-namespaces
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
This PR is to create a new package `@azure/eventgrid-namespaces`. This
new package is associated with the existing package `@azure/eventgrid`.
Earlier, we has a beta version of the `@azure/eventgrid` package and the
source code for this beta version is available in the
[`feature/eventgrid/4_13_beta_1`](https://github.com/Azure/azure-sdk-for-js/tree/feature/eventgrid/4_13_beta_1).
In this beta version, in addition to the regular
`EventGridPublisherClient`, we also have a new
[`EventGridClient`](https://github.com/Azure/azure-sdk-for-js/blob/feature/eventgrid/4_13_beta_1/sdk/eventgrid/eventgrid/src/eventGridClientV2.ts).
With this PR, we are extracting this client alone into its own new
package.
### 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?
No special design considerations to discuss.
### Are there test cases added in this PR? _(If not, why?)_
Yes.
### Provide a list of related PRs _(if any)_
NA
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
NA
### 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)_
- [X] Added a changelog (if necessary)
---------
Co-authored-by: Jeremy Meng <yumeng@microsoft.com>
### Packages impacted by this PR
- @azure/app-configuration
- @azure/cosmos
- @azure/monitor-opentelemetry
- @azure/monitor-opentelemetry-exporter
### Issues associated with this PR
- #29219
### Describe the problem that is addressed by this PR
Updates to latest `nock`.
### 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
`recorder v4` `test-credential v2` and the `template upgrade to vitest
and esm`
### Describe the problem that is addressed by this PR
ESRP step was blocking the release last week, trying again
To unblock #29016
### Packages impacted by this PR
@azure-rest/ai-personalizer
### Describe the problem that is addressed by this PR
When investigating why the live tests were failing, I discovered that
new personalizer resources are no longer able to be created:
https://learn.microsoft.com/en-us/azure/ai-services/personalizer/frequently-asked-questions
Since this package never left beta, I'm marking it as deprecated.
### Packages impacted by this PR
@azure/communication-network-traversal
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/29165
### Describe the problem that is addressed by this PR
Package is no longer maintained by service.
### Packages impacted by this PR
- @azure/api-management-custom-widgets-tools
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/29128
### Describe the problem that is addressed by this PR
Updates the code to ESM core and vitest so we can use `mime` which is
ESM only via `await import("mime")`.
### 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
- [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)
### Packages impacted by this PR
`@azure-tools/test-recorder`
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/28475
### Describe the problem that is addressed by this PR
Migrates `@azure-tools/test-recorder` to ESM, supports both vitest and
mocha.
### What's in the PR
This PR also pulls in @jeremymeng's change to update recorder file path
calculation that got reverted
https://github.com/Azure/azure-sdk-for-js/pull/28423
#### One major non-breaking change to `env`
This involves bumping recorder to 4.0.0, a new major due to the nature
of the change.
`process.env` is employed in both node and browser vitest with
playwright.
- removes dotenv dependency
- env shims for browser
- deletes karma.conf
```
Exported "env" in 3.1.0 Exported "env" in 4.0.0
node Process.env Process.env
browser Window.__env__ --No shim--
```
Depends on https://github.com/Azure/azure-sdk-for-js/pull/28917
### Exposed sanitizer types
- Enhanced the `addSanitizers` method and `SanitizerOptions` options bag
by exposing the following sanitizer types for more flexible usage:
- `FindReplaceSanitizer`: A sanitizer that finds and replaces specified
strings.
- `RegexSanitizer`: A sanitizer that uses regular expressions for
pattern matching and replacement.
- `StringSanitizer`: A sanitizer that handles string-based sanitization
tasks.
- `HeaderSanitizer`: A sanitizer specifically designed for handling HTTP
headers.
- `ConnectionStringSanitizer`: A sanitizer that securely handles
connection strings.
- `RemoveHeaderSanitizer`: A sanitizer that removes specified headers
from HTTP requests or responses.
This update aims to provide users with a more comprehensive and
customizable sanitization process.
### Breaking Changes
- The `@azure-tools/test-recorder@4.0.0` package now supports `vitest`
and `playwright` (stops support for `mocha` and `karma`), employs
`process.env` in both Node and browser environments. This aligns with
the latest testing frameworks and provides improved testing
capabilities.
- The package has been simplified by removing the `dotenv` dependency
and the `karma.conf` file, env shims for the browser. This streamlines
the package dependencies and configuration files, respectively.
- These changes introduce a new `env` strategy for all SDKs once they
migrate to ESM and depend on `@azure-tools/test-recorder` version 4, as
we employ `process.env` through vitest to access environment variables
in both Node and browser environments.
---------
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
Co-authored-by: Matthew Podwysocki <matthewp@microsoft.com>
### Packages impacted by this PR
- Core packages using ESM migration
### Issues associated with this PR
- #28940
- #28918
### Describe the problem that is addressed by this PR
Upgrade to new version of `tshy` which does not force `target` to
`ES2022` (see [PR](https://github.com/isaacs/tshy/pull/55)). This should
resolve some issues for people whose environments do not support newer
syntax (e.g. Node 14 and the Webpack 4 bundler).
### Packages impacted by this PR
- @azure/schema-registry
- @azure/schema-registry-avro
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/25221
### Describe the problem that is addressed by this PR
Updates to latest `lru-cache`
### 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
- [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)
### Packages impacted by this PR
@azure/notifications-hub
### Issues associated with this PR
Contributes to #28750 but completion requires updating all the packages
to use this
### Describe the problem that is addressed by this PR
Building off of @jeremymeng's work in #27646, this PR configures API
review files for packages containing subpath exports.
While APIView is not yet ready to support multiple json files, this
provides us with appropriate API reviews tracking any public API changes.
Follow-up PRs will add support for this in APIView, but this feels like
a quick win and step forward.
### 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?
A few alternatives, and I am open to feedback:
1. Update the EngSys script to allow multiple DocModel json files - I
chose to go with a flag to disable generating them instead, so that we
can build off of it in pieces
2. File naming convention - I already got and applied some feedback on
that, thanks Timo
### Packages impacted by this PR
- @azure/eslint-plugin-azure-sdk
### Issues associated with this PR
- #28861
### Describe the problem that is addressed by this PR
Updates to latest plugin version.
### 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
- [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)
### Packages impacted by this PR
@azure/cosmos
### Issues associated with this PR
Resolves#28954
### Describe the problem that is addressed by this PR
JSBI is a BigInt polyfill that is used by @azure/cosmos. CI has
identified that
we're a little behind.
They don't have a CHANGELOG but diffing
[v3.2.5...v4.3.0](https://github.com/GoogleChromeLabs/jsbi/compare/v3.2.5...v4.3.0)
did not show any changes that will impact our usage.
This should still be validated by the cosmos team
### Checklists
- [x] Added impacted package name to the issue description.
- [x] Does this PR need 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.)_
- [x] Added a changelog (if necessary).
Co-authored-by: Matthew Podwysocki <matthewp@microsoft.com>
### Describe the problem that is addressed by this PR
Invert the `no-test-proxy` option in our test run commands, creating a
`test-proxy` option instead. The command line parsing library dev-tool
uses, `minimist`, special cases CLI options starting with `--no-`, such
that passing `--no-test-proxy` sets the `test-proxy` option to `false`,
instead of setting the `no-test-proxy` option to `true` as our commands
assume. This fix corrects that assumption by inverting the option.
Passing `--no-test-proxy` in to the run command, as many of our
package.json scripts do, will work properly after this change.
### Packages impacted by this PR
- @azure/eslint-plugin-azure-sdk
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Moves from `mocha` to `vitest` for `eslint`.
### 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
- [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)
### Packages impacted by this PR
- @azure/notification-hubs
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/28936
### Describe the problem that is addressed by this PR
Fixes to expand the API to include the FCM V1 Message type as part of
the `Notification` type.
### 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
- [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)
### Packages impacted by this PR
`@azure-tools/test-perf`
### Describe the problem that is addressed by this PR
Making perf package public for consumption outside this repo.
This marks the initial release of the `@azure-tools/test-perf` library
to npm, providing a robust test utility framework that assists with the
performance testing of Azure SDKs for JS/TS.
### Key Concepts
1. **Introduction of PerfTest**: A test utility designed to execute
performance and stress tests for Azure SDK for JavaScript packages.
2. **Test Execution**: Tests are run asynchronously, influenced by
parameters like duration, iterations, and parallelism.
3. **Command Line Parameters**: Utilizes `minimist` for parsing command
line options into a `PerfOptionDictionary<string>` for test
configuration.
4. **Default Options**: Includes standard parameters such as `help`,
`no-cleanups`, `parallel`, `duration`, `warmup`, `iterations`,
`no-cleanup`, and `milliseconds-to-log`.
5. **Test Lifecycle**: Tests run repeatedly within the specified
`duration` and `iterations`, with a `warmup` period for runtime
optimization.
6. **Setup and Cleanup**: Features `globalSetup`/`globalCleanup` methods
for CPU-level preparation and `setup`/`cleanup` methods for
instance-specific state management.
### Packages impacted by this PR
@azure/communication-phone-numbers
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Update the Number Lookup public preview to include the Number Format
features we've been preparing for GA.
https://github.com/Azure/azure-rest-api-specs/pull/27799
### 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?
This design has been reviewed by the stewardship board
### Are there test cases added in this PR? _(If not, why?)_
yes
### Provide a list of related PRs _(if any)_
https://github.com/Azure/azure-rest-api-specs/pull/27799https://github.com/Azure/azure-sdk-for-java/pull/38885
.NET _pending_
Python _pending_
### 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
- [x] 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)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
`@azure/monitor-opentelemetry`
`@azure/monitor-opentelemetry-exporter`
### Describe the problem that is addressed by this PR
`cross-env` was removed from the devdeps of monitor-opentelemetry and
monitor-opentelemetry-exporter which causes pipeline failures when
running the test pipeline since the integration test command uses this
binary.
Builds off of Matt's work on moving to tsx in #28801 by removing the
`use-esm-workaround` flag from packages that needed it before we moved to tsx.
There's additional cleanup to be had, but I am trying not to cause a
build storm.
We are at a point where we can delete `esm` globally!
Contributes to #28617 which can be completed with a no-ci change to
remove `esm` globally
****NO_CI****
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Updates to latest dependencies and move from mocha to vitest.
### 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
- [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)
### Packages impacted by this PR
- @azure-tests/perf-monitor-opentelemetry
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Updates to latest OTEL packages
### 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
- [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)
### Packages impacted by this PR
- `@azure/opentelemetry-instrumentation-azure-sdk`
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Updates to latest OTEL
### 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
- [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)
The `azsdkjsrush` storage account has seemingly been deleted, so this
will always fail and waste effort during CI.
Tracking issue for a full fix: #28865
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Reverts back to the original for the testing ts-node for JS and TS.
### 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)_
- https://github.com/Azure/azure-sdk-for-js/pull/28801
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)
### Packages impacted by this PR
@azure/monitor-opentelemetry
### Describe the problem that is addressed by this PR
Package should be updated to the latest version and tests updated
appropriately.
### 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)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes dependency on `ts-node` and `esm` and moves in favor of using
`tsx`
### 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)
---------
Co-authored-by: Asaf Levi <asaflevi@microsoft.com>
Co-authored-by: KarolGel <138193722+KarolGel@users.noreply.github.com>
Co-authored-by: tomsft <138026577+tomsft@users.noreply.github.com>
Co-authored-by: Karolien Gellynck <kgellynck@microsoft.com>
Co-authored-by: Tom Deray <tomderay@microsoft.com>
### Packages impacted by this PR
`dev-tool`
### Issues associated with this PR
Fixes#28763
### Describe the problem that is addressed by this PR
From their CHANGELOG.md entry, the only "breaking" change is removal of
Node 12 support, so this is a simple bump.
### Packages impacted by this PR
- All
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes the git hooks for now so that we do not block our workflows with
automation.
### 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)
The Pre Push script has some scenarios which is causing issues to
developers. I am working on resolving these issues. But, In the mean
time, there must be an easy way for the developers to push their commits
to github,
As discussed with @xirzec, I am adding an environment variable to skip
these checks.
### Packages impacted by this PR
- @azure-rest/ai-document-intelligence
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes the ESM module and updates to ES2020
### 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)
---------
Co-authored-by: SDKAuto <sdkautomation@microsoft.com>
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
This PR is not related to any specific package. It is related to the fix
in the pre-push script. In the previous version of the script, there
were 2 issues reported:
1. Script was slow
2. There was a error in the line `err = error.stdout.toString();`.
The second issue is simple and straightforward. There was a missing
check. Once, it is added, the issue is resolved. The first issue is
little tricky.
I always assumed the new packages will be created from the `main` branch
in the `Azure` fork. Based on my recent conversations, it does not seem
to be valid. Some people (based on our project documentation) create the
branch from the `main` branch in their respective fork. (They do sync
their `main` branch with the `Azure` fork frequently. But, this is not
mandatory which causes the problem).As a result, sometimes I see the
difference in about 300+ commits to be validated which causes excess
time.
Now, I have fixed the issue with adding a new remote specific to prepush
tool and using that for comparison. This will reduce the number of
commits significantly which has increased the speed.
@HarshaNalluru Please approve the PR
This reverts commit 91df305c67.
### Issues associated with this PR
Fixes#28737
### Describe the problem that is addressed by this PR
Revert the pre-push hook until we can test it a bit more.
### Packages impacted by this PR
- `@azure/abort-controller`
- `@azure/core-auth`
- `@azure/core-client`
- `@azure/core-http-compat`
- `@azure/core-lro`
- `@azure/core-paging`
- `@azure/core-rest-pipeline`
- `@azure/core-sse`
- `@azure/core-tracing`
- `@azure/core-util`
- `@azure/core-xml`
- `@azure/logger`
- `@azure-rest/core-client`
- `@typespec/ts-http-runtime`
### Describe the problem that is addressed by this PR
Fix `.mts` files (used for platform mappings) not being included in
lint/format pass. Also fixed a couple of lint errors that showed up as a
result.
### Packages impacted by this PR
No specific package is impacted. This PR is to ensure that the code is
formatted before checking the code to a github repository.
### Issues associated with this PR
No
### Describe the problem that is addressed by this PR
In our repository we have several projects. When we make changes to them
and start the PR process, the build and analyze process starts. During
this process, the code formatter checks and reports any errors. In an
ideal world, it works great. But, in reality, I have found these errors
only after 30 - 45 minutes after creating the PR. This has occurred many
times and it would be great if there is a solution that can report
formatting issue before I create the 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?
A few things are considered in the current design:
1. This solution must help the developer and not create another hurdle.
So, If the developer wants to do multiple commits locally, without
worrying about formatting, he should be able to do it. (So, pre-commit
hook is not used)
2. The solution must work across multiple projects and multiple commits.
3. Direct Git hooks are the ideal solution. But, unfortunately, the
hooks cannot be distributed to the team, since git ignores everything
under `.git` folder.
4. So, I have used the rush hooks directory. So, this will be available
to all the team members who clone the repository. Now, they have 2
options. A) They could copy the hook to their `.git\hooks\` folder. B) A
better recommended solution is to execute the following command: `rush
install` which will automatically handle the linking for them
### Are there test cases added in this PR? _(If not, why?)_
No. This is a pre-push git hook
### Provide a list of related PRs _(if any)_
None
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
None
### 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)
@xirzec @deyaaeldeen @jeremymeng @joheredi @maorleger Please review and
approve the PR. Thanks
Looks like Google updated their URLs for chrome for testing downloads,
planning to retire the `hdgedl.me.gvt1.com...` URLs with
`storage.googleapis.com` URLs
It may have been deprecated for quite some time, but looks like as of
last night the old URLs have died, returning 500 instead.
As a result, puppeteer postinstall breaks the build
According to https://github.com/puppeteer/puppeteer/issues/11967
puppeteer 22.2.0 already uses the new URLs which
we can easily upgrade to.
This PR bumps the min-version to 22.2.0 across the board.
### Packages impacted by this PR
@azure-rest/communication-messages
API View =>
https://apiview.dev/Assemblies/Review/17216b4144934c31be61a27fc66f03b8?revisionId=91186996fce447488b468acfd07eb2f5&doc=False
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Azure Communication Message SDK Onboarding
### 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?)_
Yes
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### 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)_
- [x] Added a changelog (if necessary)
By conventions rollup plugins prefix virtual modules with \0. Other
plugins should not try to process those virtual modules.
This PR updates our load-source-maps plugin to ignore modules whose id
starts with "\x00" thus fixes the following warning.
```
(!) Plugin load-source-maps: TypeError: The argument 'path' must be a string, Uint8Array, or URL without null bytes. Received '\x00commonjsHelpers.js'
at open (node:internal/fs/promises:605:10)
at readFile (node:internal/fs/promises:1085:20)
at Object.load (/home/runner/work/rushstack/rushstack/jssdk/common/tools/dev-tool/src/config/rollup.base.config.ts:141:36)
at /home/runner/work/rushstack/rushstack/jssdk/common/temp/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/shared/rollup.js:1009:40
at async PluginDriver.hookFirstAndGetPlugin (/home/runner/work/rushstack/rushstack/jssdk/common/temp/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/shared/rollup.js:909:28)
at async /home/runner/work/rushstack/rushstack/jssdk/common/temp/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/shared/rollup.js:19726:33
at async Queue.work (/home/runner/work/rushstack/rushstack/jssdk/common/temp/node_modules/.pnpm/rollup@4.12.0/node_modules/rollup/dist/shared/rollup.js:20113:32)
...19 lines omitted...
```
### Packages impacted by this PR
- @azure/abort-controller
- @azure/core-auth
- @azure/core-client
- @azure-rest/core-client
- @azure/core-http-compat
- @azure/core-lro
- @azure/core-paging
- @azure/core-rest-pipeline
- @azure/core-sse
- @azure/core-tracing
- @azure/core-util
- @azure/core-xml
- @azure/logger
- @typespec/ts-http-runtime
### Issues associated with this PR
### Describe the problem that is addressed by this PR
This migrates the core packages from a hybrid of CJS and ESM to an ESM
solution using [`tshy`](https://github.com/isaacs/tshy). The core is now
ESM, implemented as a module, and projects using `tshy` to CommonJS and
ESM.
The ESM build targets we will target include:
- ESM (Node)
- Browser
- React-Native
- Bun
- Deno
This will allow each system to pick up the correct output instead of
picking the browser bundle which has happened in the past. Currently,
our bun and deno support is strictly through npm compatibility and we
are not forking logic at this point for those runtimes.
In order to support ESM, `sinon` does not allow for ESM module mocking,
so we looked for an alterative in `vitest`. This PR also migrates all
core packages stated above from Mocha/Chai for Node and Mocha/Chai/Karma
for the browser to using `vitest` for all tests. Currently, the system
builds a test bundle which targets the correct files such as those
targeted for the browser, eg `log-browser.mts` becomes `log.js` in the
compiled output.
### 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)
---------
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
Co-authored-by: Maor Leger <maorleger@users.noreply.github.com>
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
to `communication-job-router-rest` and `iot-device-update-rest` as they
are using the `dev-tool run test:node-js-test` command which runs `c8`
for code coverage.
- Switch to use esm4mocha loader by default
- Add `--use-esm-workaround=true` to packages that need more work
(mostly due to usage of `__dirname` that is no longer available in ESM)
- Change some usage of `__dirname` to `"."` when possible
- [esm4mocha] only transform modules whose format is changed
- [load-testing-rest] update tsconfig.json to be consistent with other
packages
### Packages impacted by this PR
@azure/identity
### Issues associated with this PR
Resolves#28373
### Describe the problem that is addressed by this PR
This PR addresses 3 things, all thanks to @jeremymeng's work on
esm4mocha:
1. Re-enables IBC test that was skipped due to #28373
3. Removes sinon stubbing of uuid, replacing it with recorder replacer
4. Fixes min/max tests for identity
Unfortunately we are not out of the woods regarding msal-node and esm.
We would need to get everyone migrated over
to this loader before we can upgrade msal-node repo-wide :(
### Provide a list of related PRs _(if any)_
#28556
Currently most of our '*.js' tests and sources under dist-esm/ are
transformed by `esm` package (now outdated and archived) before being
feeded to Mocha because when a package.json has `"type":
"commonjs"` thus Mocha treats `.js` files as CommonJS.
This PR takes another approach by telling Mocha that the loaded modules
under dist-esm/ are ESM via a custom loader (`esm4mocha.mjs`).
This is done mainly in two parts:
1. During resolving, this loader checks the path of resolved modules and
if it includes `"dist-esm/"` we set the format of the resolved module to
`"module"`.
2. Also in ESM the full extension is required for relative modules in
import/export declarations, so a transformation is applied
to add `".js"` extension to relative imports/exports on the fly when
loading the module.
ServiceBus integration-test:node script has been updated to use this
approach. For now, the dev-tool command is unrolled and the old
workaround is replaced by the new one:
```diff
- -r ../../../common/tools/esm-workaround -r esm
+ --loader=../../../common/tools/esm4mocha.mjs
```
In the future, the dev-tool command would be updated to use the new
workaround for the majority of our packages.
### Packages impacted by this PR
- `@azure-tools/dev-tool`
### Describe the problem addressed by this PR
New concept for customization tool I want to check in so we can test
whether it works better for our needs than the existing tool.
As a high-level overview, this tool leverages Git and its diff/merge
capabilities to take handwritten modifications to the old generated code
and apply it to new generated code after regenerating. The user will
resolve any merge conflicts if present after the fact.
### Packages impacted by this PR
- @azure/event-hubs
- @azure/service-bus
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/security/dependabot/49
### Describe the problem that is addressed by this PR
Updates with the latest `https-proxy-agent` which does not have the
vulnerability.
### 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
- [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)
### Packages impacted by this PR
- @azure/core-rest-pipeline
- @typespec/ts-http-runtime
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/security/dependabot/49
### Describe the problem that is addressed by this PR
Upgrades to the 7.x version of the `https-proxy-agent` and
`http-proxy-agent` used for our proxy pipelines.
### 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
- [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)
Jeremy Meng
Azure SDK Bot
ZiWei Chen
Matthew Podwysocki
Deyaaeldeen Almahallawi
Jackson Weber
Sarangan Rajamanickam
Driele Neves Ribeiro
hamshavathimunibyraiah
Glenn Harper
Jana R
Minh-Anh Phan
luc
EmmaZhu-MSFT
Maor Leger
chungshengfu
Harsha Nalluru
Daniel Getu
Timo van Veenendaal
Jeff Fisher
Mary Gao
KarishmaGhiya
John
Maor Leger
Erica
Hector Hernandez
koen-mertens
Yifan Zhou
Arif Ibrahim Mohamed