Skip to content

fix: remove dead nuget-version-suffix references from build-nuget-packages workflow#5061

Open
Cloud-Architect-Emma wants to merge 2 commits into
open-telemetry:mainfrom
Cloud-Architect-Emma:fix/remove-dead-nuget-version-suffix-reference
Open

fix: remove dead nuget-version-suffix references from build-nuget-packages workflow#5061
Cloud-Architect-Emma wants to merge 2 commits into
open-telemetry:mainfrom
Cloud-Architect-Emma:fix/remove-dead-nuget-version-suffix-reference

Conversation

@Cloud-Architect-Emma
Copy link
Copy Markdown

Fixes #5001

The set-nuget-version-suffix step was removed in #2772 but two dead
references remained:

  • workflow_call.outputs.nuget-version-suffix referencing
    jobs.build-nuget-packages.outputs.nuget-version-suffix
  • jobs.build-nuget-packages.outputs.nuget-version-suffix referencing
    steps.set-nuget-version-suffix.outputs.suffix

Both have been removed.

@Cloud-Architect-Emma Cloud-Architect-Emma requested a review from a team as a code owner May 11, 2026 04:50
@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

Hi @lachmatt, I've opened this PR to fix #5001. Could you approve
the CI workflows so the checks can run? Thank you!

@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

Hi @lachmatt, the CI failures are unrelated to this PR, they're
caused by a pre-existing vulnerability in SharpCompress 0.30.1
(GHSA-6c8g-7p36-r338) in TestApplication.MongoDB, which exists
on main as well.

All checks relevant to this change are passing:
-build-nuget-packages
-format native checks
-EasyCLA
-SdkVersionCheck

Happy to address anything else needed. Thank you!

Comment thread .github/workflows/release-publish.yml
@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

@lachmatt, can you please review the PR at your convenience?

@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

Hi @iskiselev, that change to release-publish.yml was accidental,
a regex side effect. I've reverted it. The PR now only removes the
stale nuget-version-suffix references from build-nuget-packages.yml.

Copy link
Copy Markdown
Contributor

@iskiselev iskiselev left a comment

Choose a reason for hiding this comment

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

@Cloud-Architect-Emma Cloud-Architect-Emma force-pushed the fix/remove-dead-nuget-version-suffix-reference branch 5 times, most recently from fa02a01 to f0fd771 Compare May 15, 2026 22:29
@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

Cloud-Architect-Emma commented May 15, 2026

@iskiselev,
Updated the PR to remove the unintended release-publish.yml change. The file has been reverted to origin/main and is no longer part of this PR. The change now only includes the intended cleanup in build-nuget-packages.yml.
Thanks for the review.

@Cloud-Architect-Emma Cloud-Architect-Emma force-pushed the fix/remove-dead-nuget-version-suffix-reference branch 2 times, most recently from 58b312a to 2e24513 Compare May 16, 2026 09:27
@Cloud-Architect-Emma
Copy link
Copy Markdown
Author

Hi @iskiselev, sorry for the confusion! The accidental change to
release-publish.yml has now been fully reverted. The PR now only
touches build-nuget-packages.yml to remove the 7 stale
nuget-version-suffix lines.

Thank you for catching that!

…kages workflow

Co-authored-by: lachmatt <lachmatt@users.noreply.github.com>
@Cloud-Architect-Emma Cloud-Architect-Emma force-pushed the fix/remove-dead-nuget-version-suffix-reference branch from 2e24513 to f294092 Compare May 16, 2026 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

build-nuget-packages mention non-existing set-nuget-version-suffix step

3 participants