Skip to content

Add workflow to create releases on tag push - #1443

Merged
mattn merged 2 commits into
masterfrom
add-release-workflow
Jul 30, 2026
Merged

Add workflow to create releases on tag push#1443
mattn merged 2 commits into
masterfrom
add-release-workflow

Conversation

@mattn

@mattn mattn commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Pushing a v* tag now creates the GitHub release automatically with generated notes (What's Changed / New Contributors / Full Changelog, same format as the v1.14.48 notes). Skips tags that already have a release.

Summary by CodeRabbit

  • New Features
    • Added an automated release workflow that creates a release when version tags (e.g., v*) are pushed.
    • Avoids creating duplicate releases by checking whether a release already exists for the tag.
    • Automatically generates release notes and verifies the tag before publishing.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 10571d38-6124-4379-a884-aab439fb2364

📥 Commits

Reviewing files that changed from the base of the PR and between 485f31f and a93a209.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/release.yaml

📝 Walkthrough

Walkthrough

Adds a GitHub Actions workflow that runs for v* tag pushes, checks for an existing release, and creates a verified GitHub release with generated notes when none exists.

Changes

Release automation

Layer / File(s) Summary
Tagged release workflow
.github/workflows/release.yaml
The workflow triggers on version tags, grants contents: write, serializes runs per tag reference, skips existing releases, and creates missing releases with tag-derived metadata and generated notes.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: a new workflow that creates releases when tags are pushed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-release-workflow

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/release.yaml:
- Around line 20-23: Update the release lookup condition around gh release view
so only an explicit “release not found” response proceeds to creation; treat
authentication, network, API, and other unexpected lookup failures as errors and
exit before the non-idempotent release creation step. Preserve the existing skip
behavior when the release already exists.
- Around line 20-24: Add a workflow-level concurrency configuration in
release.yaml using a group keyed by the release tag (GITHUB_REF_NAME), with
cancel-in-progress disabled, so runs for the same tag serialize before the
existing gh release view and gh release create steps.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 43bf2f61-cf19-418f-8b27-ecfd5fb54b1f

📥 Commits

Reviewing files that changed from the base of the PR and between 9415230 and 485f31f.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml

Comment thread .github/workflows/release.yaml Outdated
Comment thread .github/workflows/release.yaml Outdated
@mattn
mattn merged commit f9fc7aa into master Jul 30, 2026
21 checks passed
@mattn
mattn deleted the add-release-workflow branch July 30, 2026 14:18
github-actions Bot pushed a commit to rezuscloud/forgejo that referenced this pull request Aug 18, 2026
This PR contains the following updates:

| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3) | `v1.14.49` → `v1.14.50` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fmattn%2fgo-sqlite3/v1.14.50?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fmattn%2fgo-sqlite3/v1.14.49/v1.14.50?slim=true) |

---

### Release Notes

<details>
<summary>mattn/go-sqlite3 (github.com/mattn/go-sqlite3)</summary>

### [`v1.14.50`](https://github.com/mattn/go-sqlite3/releases/tag/v1.14.50): 1.14.50

[Compare Source](mattn/go-sqlite3@v1.14.49...v1.14.50)

#### What's Changed

- Handle NULL and BLOB values in json example Scan by [@&#8203;mattn](https://github.com/mattn) in [#&#8203;1441](mattn/go-sqlite3#1441)
- Add workflow to create releases on tag push by [@&#8203;mattn](https://github.com/mattn) in [#&#8203;1443](mattn/go-sqlite3#1443)
- fix: keep vtab handle registered when xDestroy fails by [@&#8203;canesin](https://github.com/canesin) in [#&#8203;1446](mattn/go-sqlite3#1446)

#### New Contributors

- [@&#8203;canesin](https://github.com/canesin) made their first contribution in [#&#8203;1446](mattn/go-sqlite3#1446)

**Full Changelog**: <mattn/go-sqlite3@v1.14.49...v1.14.50>

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - Between 12:00 AM and 03:59 AM (`* 0-3 * * *`)
- Automerge
  - Between 12:00 AM and 03:59 AM (`* 0-3 * * *`)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4zMS4wIiwidXBkYXRlZEluVmVyIjoiNDQuMzEuMCIsInRhcmdldEJyYW5jaCI6ImZvcmdlam8iLCJsYWJlbHMiOlsiZGVwZW5kZW5jeS11cGdyYWRlIiwidGVzdC9ub3QtbmVlZGVkIl19-->

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13964
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant