Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Dependency package @opentelemetry/instrumentation-redis-4 has a new version available #32342

Closed
azure-sdk opened this issue Dec 23, 2024 · 0 comments
Closed

Dependency package @opentelemetry/instrumentation-redis-4 has a new version available #32342

azure-sdk opened this issue Dec 23, 2024 · 0 comments
Labels
dependency-upgrade-required

Comments

@azure-sdk
Copy link
Collaborator

We have identified a dependency on version 0.45.0 of @opentelemetry/instrumentation-redis-4. A new version (0.46.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 rush update 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.
@mpodwysocki mpodwysocki mentioned this issue Dec 26, 2024
Merged
3 tasks
mpodwysocki added a commit that referenced this issue Dec 29, 2024
@mpodwysocki
[monitor] Update tests for OTEL (#32369)
02f964f 
### 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

- #32334
- #32335
- #32337
- #32338
- #32339
- #32340
- #32341
- #32342
- #32343
- #32344
- #32345
- #32346
- #32347

### 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dependency-upgrade-required
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mpodwysocki @azure-sdk