Bump version to 0.3.0

Signed-off-by: Dave Thaler <[email protected]>
microsoft · Aug 8, 2022 · e5a693e · e5a693e
1 parent dc384f6
commit e5a693e
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 8 deletions.
diff --git a/.github/workflows/reusable-build.yml b/.github/workflows/reusable-build.yml
@@ -169,7 +169,7 @@ jobs:
       if: matrix.configurations == 'Release' && inputs.generate_release_package == true
       working-directory: ${{env.GITHUB_WORKSPACE}}
       run: |
-        cmake -S tools\setup -B build\setup -DEBPFFORWINDOWS_PROGRAM_DATA="${{github.workspace}}\${{env.BUILD_PLATFORM}}\${{env.BUILD_CONFIGURATION}}\package_data" "-DEBPFFORWINDOWS_VERSION=0.2.0" -DCPACK_GENERATOR=WIX
+        cmake -S tools\setup -B build\setup -DEBPFFORWINDOWS_PROGRAM_DATA="${{github.workspace}}\${{env.BUILD_PLATFORM}}\${{env.BUILD_CONFIGURATION}}\package_data" "-DEBPFFORWINDOWS_VERSION=0.3.0" -DCPACK_GENERATOR=WIX
         cmake --build build\setup --target package
 
     - name: Locate the packages

diff --git a/docs/ReleaseProcess.md b/docs/ReleaseProcess.md
@@ -8,16 +8,17 @@ Note: Currently releases are not production signed.
 1. Update the version number, making sure to follow [Semantic Versioning 2.0](https://semver.org), in the following two files:
     * .github\workflows\reusable-build.yml
     * tools\nuget\ebpf-for-windows.nuspec
+    * scripts\deploy-ebpf.ps1
 2. Create a pull request with the version number changes
-3. Add a tag to the commit with the version number changes
-   ("git tag v0.2.0", "git push --tags")
-4. Once the build completes on the PR, download the
+3. Once the build completes on the PR, download the
    "ebpf-for-windows.msi" and "ebpf-for-windows nuget" build artifacts
    (accessible via the Actions tab on github)
-5. Extract the .msi and .nupkg, respectively, out of them
-6. Test the MSI manually (since not yet tested in CI/CD):
+4. Extract the .msi and .nupkg, respectively, out of them
+5. Test the MSI manually (since not yet tested in CI/CD):
     1. Copy the MSI into a VM (if not already there)
     2. Install it, and run a command or two (bpftool prog show, netsh eb sh prog) to make sure it's installed
+6. Add a tag to the commit with the version number changes
+   (e.g., "git tag v0.2.0", "git push --tags")
 7. Go to the repo on github and click on "tags" (a bit to the right of the branch combo box)
 8. Find the tag you created, and click "..." on the right and "Create release"
 9. Start uploading the .msi and .nupkg files

diff --git a/scripts/deploy-ebpf.ps1 b/scripts/deploy-ebpf.ps1
@@ -25,7 +25,7 @@ $source_directory="."
     "VCRUNTIME140D.dll")
 
 [System.Collections.ArrayList]$source_msi_files=@(
-    "ebpf-for-windows-0.2.0.msi")
+    "ebpf-for-windows-0.3.0.msi")
 
 [System.Collections.ArrayList]$source_script_files=@(
     "scripts\common.psm1",

diff --git a/tools/nuget/ebpf-for-windows.nuspec b/tools/nuget/ebpf-for-windows.nuspec
@@ -6,7 +6,7 @@
   <metadata>
     <title>eBPF for Windows SDK</title>
     <id>eBPF-for-Windows</id>
-    <version>0.2.0</version>
+    <version>0.3.0</version>
     <authors>eBPF for Windows Contributors</authors>
     <owners>eBPF for Windows Contributors</owners>
     <requireLicenseAcceptance>false</requireLicenseAcceptance>