Skip to content

Commit f35ce4f

Browse files
committed
Add documentation for version bump
If I forget the steps or somebody else does it. Signed-off-by: Daniel Schaefer <dhs@frame.work>
1 parent e6b839e commit f35ce4f

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed

contrib/release.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# New Release
2+
3+
1. Tag
4+
2. Download binaries from github action run on tag
5+
3. Sign windows exe with EV cert
6+
4. Create release with release notes and upload binaries
7+
5. Notify distribution maintainers (See README)
8+
9+
## winget
10+
11+
See: https://learn.microsoft.com/en-us/windows/package-manager/package/repository
12+
13+
```
14+
# Example with version 0.5.0
15+
16+
# Create new manifest
17+
wingetcreate update FrameworkComputer.framework_tool -u https://github.com/FrameworkComputer/framework-system/releases/download/v0.5.0/framework_tool.exe -v 0.5.0
18+
19+
winget validate .\manifests\f\FrameworkComputer\framework_tool\0.5.0
20+
21+
# Launches a new window where it installed the command
22+
# Try out some things that don't need hardware access
23+
powershell .\Tools\SandboxTest.ps1 .\manifests\f\FrameworkComputer\framework_tool\0.5.0
24+
25+
winget install --manifest .\manifests\f\FrameworkComputer\framework_tool\0.5.0
26+
27+
git add manifests/f/FrameworkComputer/framework_tool/0.5.0
28+
git commit -sm "New version: FrameworkComputer.framework_tool version 0.5.0"
29+
```

0 commit comments

Comments
 (0)