- README / CONTRIBUTING: clone from the Gitea repo. - SECURITY: Gitea has no private security advisories; report to support@fejl40.nu instead. - RELEASING: release URL on Gitea, plus a note that build.yml still uses the GitHub-only action-gh-release step, so no releases are produced on Gitea yet (server self-update via git is unaffected). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
49 lines
1.3 KiB
Markdown
49 lines
1.3 KiB
Markdown
# Pushing & Releasing
|
|
|
|
## Everyday push (rolling build)
|
|
|
|
```bash
|
|
git add .
|
|
git commit -m "Your message"
|
|
git push origin main
|
|
```
|
|
|
|
The build workflow (`.github/workflows/build.yml`) builds Windows and Linux
|
|
binaries and updates the **"Latest build (main)"** pre-release at:
|
|
`https://git.fejl40.nu/Fejl40.nu/GDPRScanner/releases/tag/latest`
|
|
|
|
> **Note:** the repository moved from GitHub to Gitea (`git.fejl40.nu`). The
|
|
> workflow still publishes with the GitHub-only `softprops/action-gh-release`
|
|
> action, so releases are **not yet produced on Gitea**. Until the workflow is
|
|
> ported to Gitea Actions, build and attach binaries manually. Server installs
|
|
> are unaffected — they self-update from `git.fejl40.nu` via git
|
|
> (see `update_gdpr.sh`).
|
|
|
|
## Versioned release
|
|
|
|
Tag the commit and push the tag:
|
|
|
|
```bash
|
|
git tag v1.6.14
|
|
git push origin main
|
|
git push origin v1.6.14
|
|
```
|
|
|
|
Actions creates a proper release named `v1.6.14` with auto-generated
|
|
release notes and the built binaries attached.
|
|
|
|
Append `-beta` or `-rc` to the tag to mark it as a pre-release:
|
|
|
|
```bash
|
|
git tag v1.6.14-beta1
|
|
git push origin v1.6.14-beta1
|
|
```
|
|
|
|
## Summary
|
|
|
|
| Action | Result |
|
|
|---|---|
|
|
| `git push origin main` | Updates the rolling `latest` pre-release |
|
|
| `git push origin v1.x.y` | Creates a new versioned release |
|
|
| `git push origin v1.x.y-beta1` | Creates a versioned pre-release |
|