Increment client preview versions

[mikeharder]

• Package Version Updates
  • Increment version of all preview client libraries which have already shipped (typically from A.B.C-preview.1 to A.B.C-preview.2)
  • Preview versions which have never shipped were unchanged
  • Non-preview versions were unchanged
• Dependency Specifier Updates
  • All dependencies on previews were pinned (e.g. ^1.0.0-preview.1 to 1.0.0-preview.1) since we allow breaking changes between previews and don't want to roll forward.
• Dependency Updates
  • The following dependency versions were updated since the packages appear to have important changes since the last release. All other dependency versions were unchanged.
  • identity
    • [Identity] Enable @azure/identity to build for the browser #4165
  • core-http
    • Fixes for a couple @azure/core-http issues found during arm-* migration #4335
  • core-arm
    • Version must align with core-http. This might be an issue in our packages where we should be using a peer dependency rather than a standard dependency.
  • core-amqp
    • Changes in core-amqp and event-hubs: [core-amqp] Implement exponential retry mechanism #4175
    • Changes in service-bus (depends on [core-amqp] Implement exponential retry mechanism #4175): [core-amqp] Implement exponential retry mechanism #4175
• Fixes Increment versions of all shipped preview client libraries #4355

[mikeharder]

/azp run js - eventhubs-client - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[weshaggard]

For my information is there an npm/rush command/tool you can use to update a version or did you update the version manually in all the projects?

[mikeharder]

For my information is there an npm/rush command/tool you can use to update a version or did you update the version manually in all the projects?

Rush has an experimental command for bumping versions, but I haven't tried it yet and I don't know if our repo is configured correctly for it:

https://rushjs.io/pages/commands/rush_version/

All the updates in this PR were made by hand. Currently the number of packages and dependencies is small enough to make this feasible, but as the repo grows I think we will want a tool to automate this.

[mikeharder]

/azp run js - eventhubs-client - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mikeharder]

/azp run js - servicebus - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[bsiegel]

Changes LGTM, let’s just make sure to get this step added to our release checklist.

[mikeharder]

Blocked on #4377

[mikeharder]

/azp run js - eventhubs-client - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mikeharder]

/azp run js - eventhubs-client - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).