Modernize release workflow for v1.9.x releases#443
Merged
jozefizso merged 11 commits intoreleases/netoffice_v1.9.8from Nov 3, 2025
Merged
Modernize release workflow for v1.9.x releases#443jozefizso merged 11 commits intoreleases/netoffice_v1.9.8from
release workflow for v1.9.x releases#443jozefizso merged 11 commits intoreleases/netoffice_v1.9.8from
Conversation
Fixed the `error NU1004: The project's runtime identifiers have changed from. Project's runtime identifiers: win-x86, lock file's runtime identifiers win7-x86.`
m-kovac
approved these changes
Nov 3, 2025
DominikPalo
approved these changes
Nov 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To continue releasing bugfixes in the
v1.9train thereleaseworkflow is modernized with support for Azure Trusted Signing and NuGet Trusted Publishing.The workflow will use federated OIDC logins to Azure and NuGet to minimize secret tokens management.
Workflow is split to two parts. Release will build and digitally signed NetOffice assemblies and it will create the legacy archive and all nuget packages. As the Azure Trusted Signing is used short lived three day certificates and the NuGet Gallery does not support the Public Trust Identity EKU yet (see NuGet/NuGetGallery#10027), developer must manually download the
certificateartifact and upload the.cerfile to NuGet Account for NetOffice.The
nuget-galleryenvironment is gated by manual approval, so the second part of the release workflow will run only after the certificate was uploaded to NuGet Gallyer account.