Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Updated docker common package version to 2.265.0 across the tasks#21408

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.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@v-dko
Copy link
Contributor

Context

Updated docker common package version to 2.265.0 across the tasks
Rmicrosoft/azure-pipelines-tasks-common-packages#448
https://mseng.visualstudio.com/AzureDevOps/_workitems/edit/2328161/

Task Name

Applicable for tasks having docker common package 2.256.0/2.264.0


Description

Updated docker common package version to 2.265.0 across the tasks


Risk Assessment (Low / Medium / High)

Low


Change Behind Feature Flag (Yes / No)

NO

Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

  • User guides, API specs, system diagrams, or runbooks are updated.

Unit Tests Added or Updated (Yes / No)

manually tested


Additional Testing Performed


Logging Added/Updated (Yes/No)

  • Appropriate log statements are added with meaningful messages.
  • Logging does not expose sensitive data.
  • Log levels are used correctly (e.g., info, warn, error).

Telemetry Added/Updated (Yes/No)

  • Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
  • Events are tagged with proper metadata for filtering and analysis.
  • Telemetry is validated in staging or test environments.

Rollback Scenario and Process (Yes/No)

  • Rollback plan is documented.

Dependency Impact Assessed and Regression Tested (Yes/No)

  • All impacted internal modules, APIs, services, and third-party libraries are analyzed.
  • Results are reviewed and confirmed to not break existing functionality.

Checklist

  • Related issue linked (if applicable)
  • Task version was bumped — seeversioning guide
  • Verified the task behaves as expected

@v-dkov-dko requested review froma team andmanolerazvan ascode ownersOctober 29, 2025 12:46
@v-dko
Copy link
ContributorAuthor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

Copy link

@nemanjarogicnemanjarogic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Please consider adding necessary details in PR description like what is reason to go to 2.265.0.

Also, consider removing unnecessary sections from description

  • Tech Design / Approach
  • Telemetry Added/Updated
  • etc.

or just answer with simple Yes/No (for example forDocumentation Changes Required and similar sections ).

Right now, the description has too many unnecessary details and it's hard to filter what is important and what is just auto generated and totally unnecessary. For example

Telemetry Added/Updated (Yes/No)Custom telemetry (e.g., counters, timers, error tracking) is added as needed.Events are tagged with proper metadata for filtering and analysis.Telemetry is validated in staging or test environments.

"Custom telemetry (e.g., counters, timers, error tracking) is added as needed" this is not true.

@v-dko
Copy link
ContributorAuthor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-dkov-dko merged commite7120b6 intomasterNov 3, 2025
11 checks passed
@v-dkov-dko deleted the users/v-dko/updateddockercommonpackagesto2.265.0 branchNovember 3, 2025 14:51
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nemanjarogicnemanjarogicnemanjarogic approved these changes

@manolerazvanmanolerazvanAwaiting requested review from manolerazvanmanolerazvan is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@v-dko@nemanjarogic

[8]ページ先頭

©2009-2025 Movatter.jp