Skip to content

Conversation

@cschuchardt88
Copy link
Member

@cschuchardt88 cschuchardt88 commented Dec 16, 2025

Description

This is easier and better release of the nuget.org publishing. Removed Release job in the main.yml file. Auto updates binary files with the current tag release version in format v1.0.0.

Note: https://github.com/actions/create-release is outdated and no longer supported. Hasn't been updated in 5 years and uses pipelines that are outdated as well.

How to use

Just create new release manually or ask @superboyiii

Change Log

  • Add File nuget.yml
  • Modified File main.yml

Type of change

  • Optimization (the change is only an optimization)
  • Style (the change is only a code style for better maintenance or standard purpose)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Unit Testing
  • Run Application
  • Local Computer Tests
  • No Testing
  • Github Actions Locally

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Copy link
Member

@erikzhang erikzhang left a comment

Choose a reason for hiding this comment

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

The current workflow is that when a major version update is detected, a release and NuGet package are automatically published. I don't want to change this to a manual process.

@cschuchardt88
Copy link
Member Author

cschuchardt88 commented Dec 17, 2025

The current workflow is that when a major version update is detected, a release and NuGet package are automatically published. I don't want to change this to a manual process.

Its no more manual than creating a tag or release draft. Its does the same thing.,

Plus its hard to currently understand current workflow. Requires sometime to process the workflow in your head.

ALSO

Note: https://github.com/actions/create-release is outdated and no longer supported. Hasn't been updated in 5 years and uses pipelines that are outdated as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants