mirror of
https://github.com/fergalmoran/flameshot.git
synced 2026-02-10 20:44:00 +00:00
2004959b4a
* fixes code fence symmetry * capitalized names in documentations * improves markdown styling of documentation
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
# Checklist for making a new release
|
|
|
|
These are the code changes that need to take place:
|
|
- [ ] Update version in `CMakeLists.txt`
|
|
- [ ] Update version and changelog at `packaging/debian/changelog`
|
|
- [ ] Update version and changelog at `packaging/rpm/flameshot.spec`
|
|
- [ ] Update `data/appdata/flameshot.metainfo.xml`
|
|
- [ ] Update macOS version in `cmake/modules/MacOSXBundleInfo.plist.in`
|
|
- [ ] Commit and push to a PR
|
|
- [ ] Merge PR to main
|
|
- [ ] Create and push git tag on main
|
|
- [ ] Manually retrigger the Github actions so it uses the latest git tag
|
|
|
|
These are the steps for actually making the release:
|
|
- [ ] Download all binaries from CI run started from PR related to code changes shown above
|
|
- [ ] Create sha256 for each binary and compare against sha256 shown in the CI to verify there was no corruption or inserted malware
|
|
- [ ] Create a new "New Release" in Github and explain changes in release notes
|
|
- [ ] Upload all binaries and sha's
|
|
- [ ] Update flatpak manifest for Flathub: https://github.com/flathub/org.flameshot.Flameshot
|
|
- [ ] Push snapcraft edge release to stable
|
|
- [ ] If this is a major release coordinate with sign path on signed windows binaries
|
|
- [ ] Update change log on [website](https://github.com/flameshot-org/flameshot-org.github.io/) `data/changelog.md`
|
|
- [ ] Update version on [website](https://github.com/flameshot-org/flameshot-org.github.io/blob/master/_coverpage.md)
|