Skip to content

Conversation

@Shewart
Copy link
Contributor

@Shewart Shewart commented Jan 17, 2026

πŸ› Hotfix: Prevent ShellUI.Core from being published separately

Problem

During the v0.1.0 release, we discovered that 3 NuGet packages were being published instead of the intended 2 packages:

  • βœ… ShellUI.CLI (intended)
  • βœ… ShellUI.Components (intended)
  • ❌ ShellUI.Core (unintended - should not be published separately)

ShellUI.Core is an internal dependency of ShellUI.Components and should not be published as a standalone package.

Solution

  1. Set IsPackable=false on ShellUI.Core.csproj to prevent it from generating a NuGet package
  2. Updated release workflow to explicitly publish only ShellUI.CLI and ShellUI.Components
  3. Updated README to reflect that only 2 packages are published

Changes

  • src/ShellUI.Core/ShellUI.Core.csproj: Added IsPackable=false
  • .github/workflows/release.yml: Updated to explicitly publish only the 2 intended packages
  • README.md: Removed ShellUI.Core from the package list in versioning documentation

Impact

  • βœ… Future releases will only publish 2 packages (as intended)
  • βœ… No breaking changes for users (they never needed ShellUI.Core directly)

Testing

  • Verified IsPackable=false prevents package generation
  • Release workflow will only find and publish the 2 intended packages

Related to: v0.1.0 release
Type: Hotfix
Priority: Medium (prevents unnecessary package publication)

- Set ShellUI.Core.IsPackable=false (it's a dependency of ShellUI.Components)
- Update release workflow to only publish ShellUI.CLI and ShellUI.Components
- Update README to reflect only 2 packages are published
- Fixes issue where 3 packages were being published instead of 2
- Set ShellUI.Core.IsPackable=false (it's a dependency of ShellUI.Components)
- Update release workflow to only publish ShellUI.CLI and ShellUI.Components
- Update README to reflect only 2 packages are published
- Fixes issue where 3 packages were being published instead of 2
@Shewart Shewart merged commit 31f4879 into main Jan 17, 2026
2 checks passed
@Shewart Shewart deleted the hotfix/v0.1.1 branch January 17, 2026 00:30
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.

2 participants