Publish-Module

Publishes a specified module from the local computer to an online gallery.
Publish-Module [-FormatVersion [<Version>]] [-IconUri [<Uri>]] [-LicenseUri [<Uri>]] [-NuGetApiKey [<String>]][-ProjectUri [<Uri>]] [-ReleaseNotes [<String[]>]] [-Repository [<String>]] [-RequiredVersion [<Version>]] [-Tags[<String[]>]] -Name* <String> [-Confirm] [-WhatIf] [<CommonParameters>]
Publish-Module [-FormatVersion [<Version>]] [-IconUri [<Uri>]] [-LicenseUri [<Uri>]] [-NuGetApiKey [<String>]][-ProjectUri [<Uri>]] [-ReleaseNotes [<String[]>]] [-Repository [<String>]] [-Tags [<String[]>]] -Path* <String>[-Confirm] [-WhatIf] [<CommonParameters>]

The Publish-Module cmdlet publishes a module to an online NuGet-based gallery by using an API key, stored as part of a user’s profile in the gallery. You can specify the module to publish either by the module’s name, or by the path to the folder containing the module.

When you specify a module by name, Publish-Module publishes the first module that would be found by running Get-Module -ListAvailable . If you specify a minimum version of a module to publish, Publish-Module publishes the first module with a version that is greater than or equal to the minimum version that you have specified.

Publishing a module requires metadata that is displayed on the gallery page for the module. Required metadata includes the module name, version, description, and author. Although most metadata is taken from the module manifest, some metadata must be specified in Publish-Module parameters, such as Tag, ReleaseNote, IconUri, ProjectUri, and LicenseUri, because these parameters match fields in a NuGet-based gallery.

Parameters
-IconUri [<Uri>]

Specifies the URL of an icon for the module. The specified icon is displayed on the gallery webpage for the module.

-FormatVersion [<Version>]
 
-LicenseUri [<Uri>]

Specifies the URL of licensing terms for the module you want to publish.

-Name <String>

Specifies the name of the module that you want to publish. Publish-Module searches for the specified module name in $Env:PSModulePath.

-NuGetApiKey [<String>]

Specifies the API key that you want to use to publish a module to the online gallery. The API key is part of your profile in the online gallery, and can be found on your user account page in the gallery. The API key is NuGet-specific functionality.

-Path <String>

Specifies the path to the module that you want to publish. This parameter accepts either the path to the folder that contains the module, or the module manifest (.psd1) file. The parameter accepts piped values from Get-Module.

-ProjectUri [<Uri>]

Specifies the URL of a webpage about this project.

-ReleaseNotes [<String[]>]

Specifies a string containing release notes or comments that you want to be available to users of this version of the module.

-Repository [<String>]

Specifies the friendly name of a repository that has been registered by running Register-PSRepository. The repository must have a PublishLocation, which is a valid NuGet URI. The PublishLocation can be set by running Set-PSRepository. The default value of this parameter is PSGallery.

-RequiredVersion [<Version>]

Specifies the exact version of a single module to publish.

-Tags [<String[]>]

Adds one or more tags to the module that you are publishing. Example tags include DesiredStateConfiguration, DSC, DSCResourceKit, or PSModule. Separate multiple tags with commas.

-Confirm [<SwitchParameter>]

  • Default value is false

Prompts you for confirmation before running the cmdlet.Prompts you for confirmation before running the cmdlet.

-WhatIf [<SwitchParameter>]

  • Default value is false

Shows what would happen if the cmdlet runs. The cmdlet is not run.Shows what would happen if the cmdlet runs. The cmdlet is not run.

<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer, PipelineVariable, and OutVariable.

Inputs

PSModuleInfo

Examples
  1. Publish a module:
    PS C:> Publish-Module -Name "MyDscModule" -NuGetApiKey "11e4b435-6cb4-4bf7-8611-5162ed75eb73"
    
       In this example, MyDscModule is published to the online gallery by using the API key to indicate the module 
       owner's online gallery account. If MyDscModule is not a valid manifest module that specifies a name, version, 
       description, and author, an error occurs.
  2. Publish a module with gallery metadata:
    PS C:> Publish-Module -Name "MyDscModule" -NuGetApiKey "11e4b435-6cb4-4bf7-8611-5162ed75eb73" -LicenseUri "http://contoso.com/license" -Tag "Active Directory","DSC" -ReleaseNote "Updated the ActiveDirectory DSC Resources to support adding users."
    
       In this example, MyDscModule is published to the online gallery by using the API key to indicate the module 
       owner's gallery account. The additional metadata provided is displayed on the webpage for the module in the 
       gallery. The owner adds two search tags for the module, relating it to Active Directory; a brief release note is 
       also added. If MyDscModule is not a valid manifest module that specifies a name, version, description, and author, 
       an error occurs.
Additional Notes
 This cmdlet runs on Windows PowerShell 3.0 or later releases of Windows PowerShell, on Windows 7 or Windows 
 2008 R2 and later releases of Windows.

 Publish-Module shows no output if a module is published successfully.
Related Links

Find-Module
Install-Module
Uninstall-Module
Update-Module