Release version v1.0.0

CHANGELOG.md

@@ -1,7 +1,9 @@
 # ChocoButler Changelog
 
 
-## Unreleased
+## [[v1.0.0](https://github.com/cokelid/ChocoButler/releases/tag/v1.0.0)] 2021-10-19
+
+Settings will NOT follow you from v0.1.7, *breaking change!*. Settings and PID files moved to new locations. New icons. New menu entry to allow restart of ChocoButler. This is version 1, the first major release!
 
 ### Added
 * New menu entry to restart ChocoButler (under 'Advanced' menu). Useful after changing settings so that they take effect.
@@ -11,6 +13,8 @@
 * Settings file now found in `%APPDATA%`
 * PID file now created in `%LOCALAPPDATA%`
 * No longer use Chocolatey icons for licensing reasons (their icons and logos are not covered by the Apache licence)
+
+
 ## [[v0.1.8](https://github.com/cokelid/ChocoButler/releases/tag/v0.1.8)] 2021-10-05
 Improvements for chocolatey packaging and more stable with Windows Server 2012
 ### Added
@@ -20,6 +24,7 @@ Improvements for chocolatey packaging and more stable with Windows Server 2012
 * More consistent temp-dir identification (for PID file) in Windows Server 2012 R2 (and elsewhere)
 * Create startup-shortcut with chocolatey's own Install-ChocolateyShortcut command, complete with nice icon
 
+
 ## [[v0.1.7](https://github.com/cokelid/ChocoButler/releases/tag/v0.1.7)] 2021-10-05
 Allow ChocoButler to update itself via package. Repair choco.exe.old problem.
 ### Added
@@ -93,3 +98,4 @@ First Release!
 
 
 
+

README.md

@@ -11,7 +11,7 @@ Rather than running upgrades on a fixed schedule, ChocoButler alerts you when up
 ## Installation & Running
 The easiest way to install ChocoButler is via Chocolately. The [package](https://community.chocolatey.org/packages/chocobutler) in Chocolatey is named `chocobutler`. Use the Chocolatey GUI and search for "chocobutler" or install via the command line with `choco install chocobutler`. The Chocolatey package adds a shortcut to the startup folder so ChocoButler starts automatically with Windows, but it will not install any start menu icons.
 
-For manual installation, [download](https://github.com/cokelid/ChocoButler/archive/refs/tags/v0.1.8.zip) the files, unzip to a folder, double-click the `chocobutler.bat` file.
+For manual installation, [download](https://github.com/cokelid/ChocoButler/archive/refs/tags/v1.0.0.zip) the files, unzip to a folder, double-click the `chocobutler.bat` file.
 
 Alternatively clone the [github repo](https://github.com/cokelid/ChocoButler.git) and run the `chocobutler.bat` file.
 
@@ -136,3 +136,4 @@ The above changes allow you to quickly test the main check->upgrade workflow, wi
 
 
 
+

chocobutler.ps1

@@ -1,7 +1,7 @@
-# Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted
+# Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted
 # Code taken from: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-powershell-1.0/ff730952(v=technet.10)
 
-$VERSION = 'v1.0.0-beta'
+$VERSION = 'v1.0.0'
 
 [void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
 [void] [System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
@@ -609,3 +609,4 @@ $appContext = New-Object System.Windows.Forms.ApplicationContext
 
 
 
+

package/ChocoButler/chocobutler.nuspec

@@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>0.1.7</version>
+    <version>1.0.0</version>
     <!-- <packageSourceUrl>Where is this Chocolatey package located (think GitHub)? packageSourceUrl is highly recommended for the community feed</packageSourceUrl>-->
     <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
     <owners>cokelid</owners>
@@ -44,7 +44,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <requireLicenseAcceptance>true</requireLicenseAcceptance>
     <projectSourceUrl>https://github.com/cokelid/ChocoButler</projectSourceUrl>
     <packageSourceUrl>https://github.com/cokelid/ChocoButler/tree/main/package/ChocoButler</packageSourceUrl>
-    <releaseNotes>Allow ChocoButler to update itself via package. Repair choco.exe.old problem. Improvements for chocolatey packaging. More stable with Windows Server 2012 when updating.</releaseNotes>
+    <releaseNotes>https://github.com/cokelid/ChocoButler/blob/main/CHANGELOG.md#v100-2021-10-19</releaseNotes>
     <docsUrl>https://github.com/cokelid/ChocoButler#readme</docsUrl>
     <bugTrackerUrl>https://github.com/cokelid/ChocoButler/issues</bugTrackerUrl>
     <tags>ChocoButler Chocolatey choco chocolatey-automatic</tags>
@@ -74,3 +74,4 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
 
 
 
+