Skip to content

Bump Microsoft.ApplicationInsights from 2.20.0 to 2.21.0#17733

Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/nuget/Microsoft.ApplicationInsights-2.21.0
Closed

Bump Microsoft.ApplicationInsights from 2.20.0 to 2.21.0#17733
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/nuget/Microsoft.ApplicationInsights-2.21.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Jul 21, 2022

Bumps Microsoft.ApplicationInsights from 2.20.0 to 2.21.0.

Changelog

Sourced from Microsoft.ApplicationInsights's changelog.

Version 2.21.0

  • no changes since beta.

Version 2.21.0-beta3

Version 2.21.0-beta2

Version 2.21.0-beta1

Version 2.20

Version 2.20.0-beta1

Version 2.19.0

  • Support for .Net6

Version 2.19.0-beta1

Version 2.18.0

Version 2.18.0-beta3

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Jul 21, 2022
@ghost ghost assigned TravisEz13 Jul 21, 2022
@daxian-dbw
Copy link
Copy Markdown
Member

Build failure:

/home/vsts/work/1/s/src/System.Management.Automation/utils/Telemetry.cs(146,17): error CS0618: 'TelemetryConfiguration.InstrumentationKey.set' is obsolete: 'InstrumentationKey based global ingestion is being deprecated. Use TelemetryConfiguration.ConnectionString. See microsoft/ApplicationInsights-dotnet#2560 for more details.' [/home/vsts/work/1/s/src/System.Management.Automation/System.Management.Automation.csproj]

@JamesWTruher It looks we need to update the telemetry code in order to move to the new version of Microsoft.ApplicationInsights.

@ghost ghost added the Review - Needed The PR is being reviewed label Aug 2, 2022
@ghost
Copy link
Copy Markdown

ghost commented Aug 2, 2022

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

Bumps [Microsoft.ApplicationInsights](https://github.com/Microsoft/ApplicationInsights-dotnet) from 2.20.0 to 2.21.0.
- [Release notes](https://github.com/Microsoft/ApplicationInsights-dotnet/releases)
- [Changelog](https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/CHANGELOG.md)
- [Commits](microsoft/ApplicationInsights-dotnet@2.20.0...2.21.0)

---
updated-dependencies:
- dependency-name: Microsoft.ApplicationInsights
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/nuget/Microsoft.ApplicationInsights-2.21.0 branch from c314236 to b90eff7 Compare August 3, 2022 05:24
@pull-request-quantifier-deprecated
Copy link
Copy Markdown

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

JamesWTruher added a commit to JamesWTruher/PowerShell-1 that referenced this pull request Aug 15, 2022
@TravisEz13
Copy link
Copy Markdown
Member

@dependabot close

@dependabot dependabot bot closed this Aug 15, 2022
@dependabot dependabot bot deleted the dependabot/nuget/Microsoft.ApplicationInsights-2.21.0 branch August 15, 2022 18:21
@ghost ghost removed the Review - Needed The PR is being reviewed label Aug 15, 2022
github-actions bot pushed a commit that referenced this pull request Aug 18, 2022
TravisEz13 pushed a commit to TravisEz13/PowerShell that referenced this pull request Oct 13, 2022
TravisEz13 added a commit that referenced this pull request Oct 13, 2022
…#18271)

Replaces dependabot PR #17733

Co-authored-by: James Truher [MSFT] <jimtru@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log Extra Small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants