Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More
Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More
Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More
Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

1,535

Downloads of v 3.0.31:

579

Last Update:

21 Jul 2019

Package Maintainer(s):

Software Author(s):

  • Nick Spreitzer

Tags:

git semver powershell

whats-new

  • 1
  • 2
  • 3

3.0.31 | Updated: 21 Jul 2019

Downloads:

1,535

Downloads of v 3.0.31:

579

Maintainer(s):

Software Author(s):

  • Nick Spreitzer

Tags:

git semver powershell

whats-new 3.0.31

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install whats-new, run the following command from the command line or from PowerShell:

>

To upgrade whats-new, run the following command from the command line or from PowerShell:

>

To uninstall whats-new, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade whats-new -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade whats-new -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install whats-new
  win_chocolatey:
    name: whats-new
    version: '3.0.31'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'whats-new' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.0.31'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller whats-new
{
    Name     = "whats-new"
    Version  = "3.0.31"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'whats-new':
  ensure   => '3.0.31',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 23 Aug 2020.

Description

PowerShell functions for versioning a git repo with tags and more!

chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop'
$appDataFolder = "$env:LocalAppData\$env:ChocolateyPackageName\$env:ChocolateyPackageVersion"
if (-Not (Test-Path $appDataFolder)) {
  New-Item $appDataFolder -ItemType Directory | Out-Null
}

Get-ChildItem -Path "$env:ChocolateyPackageFolder" -Exclude "*.choco*","*.nu*" | Copy-Item -Destination $appDataFolder -Container -Recurse
Write-Debug "Copied contents of '$env:ChocolateyPackageFolder' to '$appDataFolder'"

$psModuleFolder = "$home\Documents\PowerShell\Modules\$env:ChocolateyPackageName"

if (-Not (Test-Path $psModuleFolder)) {
  New-item $psModuleFolder -ItemType Directory | Out-Null
  Write-Debug "Created new module directory: '$psModuleFolder'"
} 

$originalManifest = Get-Item -Path "$env:ChocolateyPackageFolder\$env:ChocolateyPackageName.psd1"
Copy-Item -Path $originalManifest -Destination $psModuleFolder -Force
Write-Debug "Copied '$originalManifest' to '$psModuleFolder'"

$deployedManifestPath = "$psModuleFolder\$env:ChocolateyPackageName.psd1"
(Get-Content $deployedManifestPath).Replace('<APP_DATA>', $appDataFolder) | Set-Content $deployedManifestPath

$oldInstalls = Get-ChildItem -Path "$env:LocalAppData\$env:ChocolateyPackageName" -Directory | 
  Sort-Object -Descending -Property @{Expression={([Version]$_.Name)};} |
  Select-Object -Skip 2

if ($null -ne $oldInstalls) {
  $oldInstalls | ForEach-Object { Write-Debug "Attempting to remove old install: $_.FullName" }
  $oldInstalls | Remove-Item -Recurse -Force -ErrorAction Ignore
}
chocolateyuninstall.ps1 
$ErrorActionPreference = 'Stop'
$psModuleFolder = "$home\Documents\PowerShell\Modules\$env:ChocolateyPackageName"
Write-Debug "Removing: $psModuleFolder"
Remove-Item $psModuleFolder -Force -Recurse

$appDataFolder = "$env:LocalAppData\$env:ChocolateyPackageName"
$oldInstalls = Get-ChildItem -Path $appDataFolder -Directory | Sort-Object
foreach ($install in $oldInstalls) {
  try {
    Write-Debug "Removing: $($install.FullName)"
    Remove-Item $($install.FullName) -Force -Recurse
  } catch {
    Write-Warning "Unable to remove $($install.FullName). You will have to do this manually."
  }
}

if (-Not(Test-Path "$appDataFolder\*")) {
  Remove-Item $appDataFolder -Force -Recurse
}
JetBrains.Annotations.dll 
md5: 8CA2B5E55458CB066D2DD1A1EE2E2C58 | sha1: 6E11A97D5186DD055A054EC8F35059A0ED722113 | sha256: E76983D2F4FBEDB4CF2494186EA53418ECFF0059239EC7B16219A82C6D65CACB | sha512: 9AFAFFA655B568F68B9358E54EAD02AF24CF67C3F94861F58286A06EBE7ECFBE96BD966FF40F11649607B80F45D745611F8725FFFE78AC5A35B3F30E7999086D
LICENSE.md 
MIT License

Copyright (c) 2017 Nick Spreitzer

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
script-modules\GitVersioning.psm1 
<# 
.SYNOPSIS
  Adds a new major version tag to the current git repository.
.DESCRIPTION
  Finds the most recent semantic version tag in the current git repository, increments the major version, and creates
  a new tag based on this new version. 
.PARAMETER Message
  The message to associate with the new tag.
.PARAMETER CurrentBranchOnly
  Restricts the search for prior version tags to the current branch. By default all branches are searched.
#>
function Add-MajorVersionTag {
  Param (
    [Parameter(Mandatory = $true, Position = 0)][string]$Message,
    [switch]$CurrentBranchOnly
  )
  $elements = GetLatestVersionElements -CurrentBranchOnly:$CurrentBranchOnly
  $major = [int]::Parse($($elements[0]))
  $major++
  $NewTag = "v$major.0.0"
  git tag -a $NewTag -m $Message 
  WriteSuccessMessage $($elements[3]) $NewTag $Message
}

<# 
.SYNOPSIS
  Adds a new minor version tag to the current git repository.
.DESCRIPTION
  Finds the most recent semantic version tag in the current git repository, increments the minor version, and creates
  a new tag based on this new version. 
.PARAMETER Message
  The message to associate with the new tag.
.PARAMETER CurrentBranchOnly
  Restricts the search for prior version tags to the current branch. By default all branches are searched.
#>
function Add-MinorVersionTag {
  Param (
    [Parameter(Mandatory = $true, Position = 0)][string]$Message,
    [switch]$CurrentBranchOnly
  )
  $elements = GetLatestVersionElements -CurrentBranchOnly:$CurrentBranchOnly
  $minor = [int]::Parse($($elements[1]))
  $minor++
  $NewTag = "v$($elements[0]).$minor.0"
  git tag -a $NewTag -m $Message 
  WriteSuccessMessage $($elements[3]) $NewTag $Message
}

<# 
.SYNOPSIS
  Adds a new patch version tag to the current git repository.
.DESCRIPTION
  Finds the most recent semantic version tag in the current git repository, increments the patch version, and creates
  a new tag based on this new version. 
.PARAMETER Message
  The message to associate with the new tag.
.PARAMETER CurrentBranchOnly
  Restricts the search for prior version tags to the current branch. By default all branches are searched.
#>
function Add-PatchVersionTag {
  Param (
    [Parameter(Mandatory = $true, Position = 0)][string]$Message,
    [switch]$CurrentBranchOnly
  )
  $elements = GetLatestVersionElements -CurrentBranchOnly:$CurrentBranchOnly
  $patch = [int]::Parse($($elements[2]))
  $patch++
  $NewTag = "v$($elements[0]).$($elements[1]).$patch"
  git tag -a $NewTag -m $Message 
  WriteSuccessMessage $($elements[3]) $NewTag $Message
}

<# 
.SYNOPSIS
  Adds a new semantic version tag to the current git repository.
.DESCRIPTION
  Creates a new semantic version tag to the current git respository based on the provided version string.
.PARAMETER Tag
  The new semantic version tag to apply. Must be in the format 'v0.0.0'.
.PARAMETER Message
  The message to associate with the new tag.
#>
function New-VersionTag {
  Param (
    [Parameter(Mandatory = $true, Position = 0)][string]$Tag,
    [Parameter(Mandatory = $true, Position = 1)][string]$Message
  )

  if ($Tag -notmatch "v[0-9]+\.[0-9]+\.[0-9]+") {
    throw "$Tag is not a valid version number. Use the format 'v1.2.3'."
  }

  git tag -a $NewTag -m $Message 
  Write-Host "New tag created`: $Tag $Message" -ForegroundColor Cyan
}

function WriteSuccessMessage {
  param(
    [Parameter(Mandatory = $true, Position = 0)][string]$OldTag,
    [Parameter(Mandatory = $true, Position = 1)][string]$NewTag,
    [Parameter(Mandatory = $true, Position = 2)][string]$Message
  )
  Write-Host "Version Incremented`: $OldTag --> $NewTag $Message" -ForegroundColor Cyan
}

function GetLatestVersionElements {
  param (
    [switch]$CurrentBranchOnly
  )

  if ($CurrentBranchOnly) {
    $lastTag = git describe
    $index = $lastTag.indexOf('-')
    if ($index -lt 0) {
      $lastTag.Substring(1).split('.') # return array of version numbers
      $lastTag.Substring(1) # return the unsplit original
    } else {
      $lastTag.Substring(1, $index - 1).split('.') # return array of version numbers
      $lastTag.Substring(1, $index - 1) # return the unsplit original
    }
  } else {
    $lastTag = git for-each-ref refs/tags/v* --format="%(refname:short)" --sort=-v:refname --count=1
    if ($null -eq $lastTag) { throw "Couldn't find any previous version to increment!" }
    $lastTag.Substring(1).split('.') # return array of version numbers
    $lastTag # return the unsplit original
  }
}

Export-ModuleMember *-*
script-modules\OpenSolution.psm1 
<#
.SYNOPSIS
  Recursively searches for the first `.sln` file and opens it using the default application, usually Visual Studio. 
.PARAMETER RootDirectory
  The directory to search. Defaults to the current directory. 
#>
function Open-Solution {
  [Alias('sln')]
  param (
    [string]$RootDirectory = $PWD
  )

  $solutions = Get-ChildItem -Recurse -Path $RootDirectory -Filter "*.sln"
  if ($solutions.Count -eq 1) {
    Invoke-Item $solutions.FullName
  }
  elseif ($solutions.Count -eq 0) {
    Write-Host "I couldn't find any solution files here!" -ForegroundColor Red
  }
  elseif ($solutions.Count -gt 1) {
    Write-Host "I found more than 1 solution. Which one do you want to open?" -ForegroundColor Yellow
    $solutions | Format-Table @{ Label="Solutions"; Expression={" --> $_"} }
  }
}

Export-ModuleMember -Function * -Alias *
script-modules\RemoveLocalBranches.psm1 
<#
.SYNOPSIS
  Deletes all local git branches in the current respository, other than master.
.DESCRIPTION
  Deletes all local git branches in the current respository, other than master. By default, unmerged branches
  are ignored. Use -Force to delete all non-master branches regardless of merge status.
.PARAMETER Force
  Deletes all braches regardless of merge status.
#>
function Remove-LocalBranches ([switch]$Force) {
  git branch |
    Where-Object { $_ -notmatch '(^\*)|(^. master$)' } |
    ForEach-Object { git branch $(if($Force) { '-D' } else { '-d' }) $_.Substring(2) }
}

Export-ModuleMember *-*
script-modules\RemoveModuleManifestComments.psm1 
<#
.SYNOPSIS
  Removes comments from module manifest files.
.DESCRIPTION
  When you use the New-ModuleManifest cmdlet to create a module manifest, it generates a lot of comments that you may not want to keep. This
  function strips away that noise and makes your manifest easy to read.
.INPUTS
  You can pipe ine a string containing the file path of a PowerShell module manifest file.
.PARAMETER ManifestPath
  The path to the module manifest file.
.PARAMETER NoConfirm
  Do not confirm before overwriting the manifest file.
#>
function Remove-ModuleManifestComments {
  [CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = 'High')]
  param (
    [Parameter(Mandatory = $true, ValueFromPipeline = $true, Position = 0)][string]$ManifestPath,
    [switch]$NoConfirm
  )

  $originalManifestContent = Get-Content $ManifestPath
  $cleanManifest = @()
  
  $originalManifestContent | ForEach-Object { 
    if ($_ -match "(?(?=.*#)(.*(?=#))|(.*))" -and -not [string]::IsNullOrWhiteSpace($Matches[0])) { 
      $cleanManifest += $Matches[0]
    } 
  }
  
  for ($i = 1; $i -le $cleanManifest.Length - 2; $i++) {
    if ($cleanManifest[$i][0] -ne "`t") {
      $cleanManifest[$i] = "`t$($cleanManifest[$i])"
    }
  }
  
  $query = "This action will overwrite the existing module manifest file. (And make it look nicer in the process.) Continue?"
  if ($NoConfirm -or $PSCmdlet.ShouldContinue($query, "*****Warning*****")) {
    Set-Content -Path $ManifestPath -Value $cleanManifest
  }
}

Export-ModuleMember *-*
System.Management.Automation.dll 
md5: A1436375A7C20FA0A993AF4EC9FF9DCA | sha1: FB69D54552F5C6B3F9D56D0B536326791F5D4416 | sha256: 4079AAF1C6C1B752EC8AE1FCCAB5FFA100DADF5D85EF679FF9039F73AD1E6B9E | sha512: D2B50319C00275C5CBC3457D7D6D6A83DE68ABB3C189BCA7790E3C1D80E81D7A42E8CA4BFB495063EF0D5620800821CAC6718E16AF624024FB7F99E45046F75C
Verification.md 
Verification

Verification is intended to assist the Chocolatey moderators and  community in verifying that this package's contents are trustworthy.

This package is published by the Nick Spreitzer himself.
whats-new.psd1 
@{
	ModuleVersion = '3.0.31'
	GUID = '861e5d28-8348-47d3-a2f6-cdd23e33bb55'
	Author = 'Nick Spreitzer'
	CompanyName = 'RAWR! Productions'
	Copyright = '(c) 2019 Nick Spreitzer. All rights reserved.'
	NestedModules = @('<APP_DATA>\script-modules\GitVersioning.psm1', 
	               '<APP_DATA>\script-modules\OpenSolution.psm1', 
	               '<APP_DATA>\script-modules\RemoveLocalBranches.psm1', 
	               '<APP_DATA>\script-modules\RemoveModuleManifestComments.psm1', 
	               '<APP_DATA>\WhatsNew.dll')
	FunctionsToExport = 'Add-MajorVersionTag', 'Add-MinorVersionTag', 'Add-PatchVersionTag', 
	               'New-VersionTag', 'WriteSuccessMessage', 'GetLatestVersionElements', 
	               'Open-Solution', 'Remove-LocalBranches', 
	               'Remove-ModuleManifestComments'
	CmdletsToExport = 'Export-BinaryCmdletAliases', 'Export-BinaryCmdletNames', 
	               'Export-PSScriptAliases', 'Export-PSScriptFunctionNames'
	VariablesToExport = '*'
	AliasesToExport = 'sln'
	PrivateData = @{
	    PSData = @{
	    } 
	} 
}
WhatsNew.deps.json 
{
  "runtimeTarget": {
    "name": ".NETStandard,Version=v2.0/",
    "signature": "251e8d43f4dbd961e4ba3adf9faaff752c5ee996"
  },
  "compilationOptions": {},
  "targets": {
    ".NETStandard,Version=v2.0": {},
    ".NETStandard,Version=v2.0/": {
      "WhatsNew/1.0.0": {
        "dependencies": {
          "JetBrains.Annotations": "2019.1.1",
          "NETStandard.Library": "2.0.3",
          "PowerShellStandard.Library": "5.1.0"
        },
        "runtime": {
          "WhatsNew.dll": {}
        }
      },
      "JetBrains.Annotations/2019.1.1": {
        "runtime": {
          "lib/netstandard2.0/JetBrains.Annotations.dll": {
            "assemblyVersion": "2019.1.1.0",
            "fileVersion": "2019.1.1.0"
          }
        }
      },
      "Microsoft.NETCore.Platforms/1.1.0": {},
      "NETStandard.Library/2.0.3": {
        "dependencies": {
          "Microsoft.NETCore.Platforms": "1.1.0"
        }
      },
      "PowerShellStandard.Library/5.1.0": {
        "runtime": {
          "lib/netstandard2.0/System.Management.Automation.dll": {
            "assemblyVersion": "3.0.0.0",
            "fileVersion": "5.1.0.0"
          }
        }
      }
    }
  },
  "libraries": {
    "WhatsNew/1.0.0": {
      "type": "project",
      "serviceable": false,
      "sha512": ""
    },
    "JetBrains.Annotations/2019.1.1": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-y4RFn+HZ7BekqIx+uXuVAvh80quYNiu86oRG2QztmFXQ2mm1lprb7xNawZdFfLxBAh8BQUkSQdO0Itanal8DbQ==",
      "path": "jetbrains.annotations/2019.1.1",
      "hashPath": "jetbrains.annotations.2019.1.1.nupkg.sha512"
    },
    "Microsoft.NETCore.Platforms/1.1.0": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-MVxohgkHpEqP04QSezDy32SdtKk6x23tugkvYxwEwUPHQnnVoEnOs1XVNOWrCS/Vm5owMgCnjAPiYfFjnDnibw==",
      "path": "microsoft.netcore.platforms/1.1.0",
      "hashPath": "microsoft.netcore.platforms.1.1.0.nupkg.sha512"
    },
    "NETStandard.Library/2.0.3": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-st47PosZSHrjECdjeIzZQbzivYBJFv6P2nv4cj2ypdI204DO+vZ7l5raGMiX4eXMJ53RfOIg+/s4DHVZ54Nu2A==",
      "path": "netstandard.library/2.0.3",
      "hashPath": "netstandard.library.2.0.3.nupkg.sha512"
    },
    "PowerShellStandard.Library/5.1.0": {
      "type": "package",
      "serviceable": true,
      "sha512": "sha512-iYaRvQsM1fow9h3uEmio+2m2VXfulgI16AYHaTZ8Sf7erGe27Qc8w/h6QL5UPuwv1aXR40QfzMEwcCeiYJp2cw==",
      "path": "powershellstandard.library/5.1.0",
      "hashPath": "powershellstandard.library.5.1.0.nupkg.sha512"
    }
  }
}
WhatsNew.dll 
md5: 62BA342AFF59B09D335133AEEF6C57F7 | sha1: 827CF3C1C5D6E8A173E9CEF75808F66C86BB2222 | sha256: 94950223B5FD44C550417620AD2903D0ED4A5D3F50450F10845F0E3CEC7EDF59 | sha512: 917BE3C9E5292CCD8144EC07CEB1D564EBBAD449CFB2D9A4561F78E0E03ED3B1770B4C4D9719035632F3D718F725F34C699EEA5FC97D5CC02F565DFC60002F21
WhatsNew.dll-Help.xml 
<?xml version="1.0" encoding="utf-8"?>
<helpItems schema="maml" xmlns="http://msh">
  <!-- Cmdlet: Export-BinaryCmdletAliases -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-BinaryCmdletAliases</command:name>
      <command:verb>Export</command:verb>
      <command:noun>BinaryCmdletAliases</command:noun>
      <maml:description>
        <maml:para>Extracts cmdlet aliases from a given module.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>Returns a list of all cmdlet aliases contained within a specified binary cmdlet module.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-BinaryCmdletAliases</maml:name>
        <!-- Parameter: ModuleInfo -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
          <maml:name>ModuleInfo</maml:name>
          <maml:description>
            <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
          </maml:description>
          <command:parameterValue required="true">PSModuleInfo</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: ModuleInfo -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
        <maml:name>ModuleInfo</maml:name>
        <maml:description>
          <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
        </maml:description>
        <command:parameterValue required="true">PSModuleInfo</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues />
    <maml:relatedLinks>
      <maml:navigationLink>
        <maml:linkText>The whats-new wiki.</maml:linkText>
        <maml:uri>https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs</maml:uri>
      </maml:navigationLink>
    </maml:relatedLinks>
  </command:command>
  <!-- Cmdlet: Export-BinaryCmdletNames -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-BinaryCmdletNames</command:name>
      <command:verb>Export</command:verb>
      <command:noun>BinaryCmdletNames</command:noun>
      <maml:description>
        <maml:para>Extracts cmdlet names from a given module.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>Returns a list of all cmdlet names contained within a specified binary cmdlet module.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-BinaryCmdletNames</maml:name>
        <!-- Parameter: ModuleInfo -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
          <maml:name>ModuleInfo</maml:name>
          <maml:description>
            <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
          </maml:description>
          <command:parameterValue required="true">PSModuleInfo</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: ModuleInfo -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
        <maml:name>ModuleInfo</maml:name>
        <maml:description>
          <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
        </maml:description>
        <command:parameterValue required="true">PSModuleInfo</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.Management.Automation.PSModuleInfo</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The PSModuleInfo from which to extract cmdlet names</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues />
    <maml:relatedLinks>
      <maml:navigationLink>
        <maml:linkText>The whats-new wiki.</maml:linkText>
        <maml:uri>https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs</maml:uri>
      </maml:navigationLink>
    </maml:relatedLinks>
  </command:command>
  <!-- Cmdlet: Export-PSScriptAliases -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-PSScriptAliases</command:name>
      <command:verb>Export</command:verb>
      <command:noun>PSScriptAliases</command:noun>
      <maml:description>
        <maml:para>Extracts aliases from a given PowerShell script.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>Returns a list of all aliases contained within a specified PowerShell script.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-PSScriptAliases</maml:name>
        <!-- Parameter: ScriptFile -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
          <maml:name>ScriptFile</maml:name>
          <maml:description>
            <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: ScriptFile -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
        <maml:name>ScriptFile</maml:name>
        <maml:description>
          <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues />
    <maml:relatedLinks>
      <maml:navigationLink>
        <maml:linkText>The whats-new wiki.</maml:linkText>
        <maml:uri>https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs</maml:uri>
      </maml:navigationLink>
    </maml:relatedLinks>
  </command:command>
  <!-- Cmdlet: Export-PSScriptFunctionNames -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-PSScriptFunctionNames</command:name>
      <command:verb>Export</command:verb>
      <command:noun>PSScriptFunctionNames</command:noun>
      <maml:description>
        <maml:para>Extracts function names from a given PowerShell script.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>Returns a list of all function names contained within a specified PowerShell script.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-PSScriptFunctionNames</maml:name>
        <!-- Parameter: ScriptFile -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
          <maml:name>ScriptFile</maml:name>
          <maml:description>
            <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: ScriptFile -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="named">
        <maml:name>ScriptFile</maml:name>
        <maml:description>
          <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The PowerShell script file from which to extract all function names.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues />
    <maml:relatedLinks>
      <maml:navigationLink>
        <maml:linkText>The whats-new wiki.</maml:linkText>
        <maml:uri>https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs</maml:uri>
      </maml:navigationLink>
    </maml:relatedLinks>
  </command:command>
</helpItems>
WhatsNew.xml 
<?xml version="1.0"?>
<doc>
    <assembly>
        <name>WhatsNew</name>
    </assembly>
    <members>
        <member name="T:WhatsNew.ExportBinaryCmdletAliasesCmdlet">
            <summary>
            <para type="synopsis">Extracts cmdlet aliases from a given module.</para>
            <para type="description">Returns a list of all cmdlet aliases contained within a specified binary cmdlet module.</para>
            <para type="link" uri="https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs">The whats-new wiki.</para>
            </summary>
        </member>
        <member name="P:WhatsNew.ExportBinaryCmdletAliasesCmdlet.ModuleInfo">
            <summary>
            <para type="description">The PSModuleInfo from which to extract cmdlet names</para>
            </summary>
        </member>
        <member name="M:WhatsNew.ExportBinaryCmdletAliasesCmdlet.ProcessRecord">
            <inheritdoc />
        </member>
        <member name="T:WhatsNew.ExportBinaryCmdletNamesCmdlet">
            <summary>
            <para type="synopsis">Extracts cmdlet names from a given module.</para>
            <para type="description">Returns a list of all cmdlet names contained within a specified binary cmdlet module.</para>
            <para type="link" uri="https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs">The whats-new wiki.</para>
            </summary>
        </member>
        <member name="P:WhatsNew.ExportBinaryCmdletNamesCmdlet.ModuleInfo">
            <summary>
            <para type="description">The PSModuleInfo from which to extract cmdlet names</para>
            </summary>
        </member>
        <member name="M:WhatsNew.ExportBinaryCmdletNamesCmdlet.ProcessRecord">
            <inheritdoc />
        </member>
        <member name="T:WhatsNew.ExportPSScriptAliasesCmdlet">
            <summary>
            <para type="synopsis">Extracts aliases from a given PowerShell script.</para>
            <para type="description">Returns a list of all aliases contained within a specified PowerShell script.</para>
            <para type="link" uri="https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs">The whats-new wiki.</para>
            </summary>
        </member>
        <member name="P:WhatsNew.ExportPSScriptAliasesCmdlet.ScriptFile">
            <summary>
            <para type="description">The PowerShell script file from which to extract all function names.</para>
            </summary>
        </member>
        <member name="M:WhatsNew.ExportPSScriptAliasesCmdlet.ProcessRecord">
            <inheritdoc />
        </member>
        <member name="T:WhatsNew.ExportPSScriptFunctionNamesCmdlet">
            <summary>
            <para type="synopsis">Extracts function names from a given PowerShell script.</para>
            <para type="description">Returns a list of all function names contained within a specified PowerShell script.</para>
            <para type="link" uri="https://github.com/refactorsaurusrex/whats-new/wiki/Cmdlet-Docs">The whats-new wiki.</para>
            </summary>
        </member>
        <member name="P:WhatsNew.ExportPSScriptFunctionNamesCmdlet.ScriptFile">
            <summary>
            <para type="description">The PowerShell script file from which to extract all function names.</para>
            </summary>
        </member>
        <member name="M:WhatsNew.ExportPSScriptFunctionNamesCmdlet.ProcessRecord">
            <inheritdoc />
        </member>
    </members>
</doc>

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
whats-new 3.0.31 579 Sunday, July 21, 2019 Approved
whats-new 2.0.24 257 Monday, October 15, 2018 Approved
whats-new 1.0.23 307 Wednesday, February 28, 2018 Approved
whats-new 1.0.0 307 Monday, February 12, 2018 Approved

This package has no dependencies.

Discussion for the whats-new Package

Ground Rules:

  • This discussion is only about whats-new and the whats-new package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or whats-new, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus