github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-09 10:45:04 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[PR #4306] [MERGED] Add an action to automatically generate release PRs #5311

New Issue
Closed
opened 2026-02-28 21:10:23 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:10:23 -06:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4306
Author: @jfdoming
Created: 2/6/2025
Status: ✅ Merged
Merged: 2/6/2025
Merged by: @jfdoming

Base: master ← Head: jfdoming/auto-generate-release-prs

📝 Commits (3)

  • 9986196 Add an action to automatically generate release PRs
  • fc8b5ed Add release notes
  • 8629f1e PR feedback: error handling

📊 Changes

3 files changed (+67 additions, -0 deletions)

View changed files

➕ .github/actions/bump-package-versions (+26 -0)
➕ .github/workflows/generate-release-pr.yml (+35 -0)
➕ upcoming-release-notes/4306.md (+6 -0)

📄 Description

Slowly trying to make the release process easier. To start, I wrote a script+manually-triggered action which will automatically create a release PR for the "next" version and bump all package.json files to that version. If you don't specify a version, it infers it using this logic which to me seems to mirror how we already do releases (pseudocode):

if (day_of_month <= 25) {
  patchVersion++;
} else {
  patchVersion = 0;
  minorVersion = next_month();
  majorVersion = year_of_next_month();
}

See this test run which generated https://github.com/jfdoming/actual/pull/5.

I'm thinking eventually we can move the release note generation to this action as well and save an extra round trip with CI! It would also be nice to automatically generate the release docs. One day...

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/4306 **Author:** [@jfdoming](https://github.com/jfdoming) **Created:** 2/6/2025 **Status:** ✅ Merged **Merged:** 2/6/2025 **Merged by:** [@jfdoming](https://github.com/jfdoming) **Base:** `master` ← **Head:** `jfdoming/auto-generate-release-prs` --- ### 📝 Commits (3) - [`9986196`](https://github.com/actualbudget/actual/commit/9986196bebdd804223aa3e1130b8de5f53443b70) Add an action to automatically generate release PRs - [`fc8b5ed`](https://github.com/actualbudget/actual/commit/fc8b5ed165beb78290146e4af8efa8c6dbea9cb2) Add release notes - [`8629f1e`](https://github.com/actualbudget/actual/commit/8629f1e04b7909be287821ff60fbc1107be15e5d) PR feedback: error handling ### 📊 Changes **3 files changed** (+67 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/actions/bump-package-versions` (+26 -0) ➕ `.github/workflows/generate-release-pr.yml` (+35 -0) ➕ `upcoming-release-notes/4306.md` (+6 -0) </details> ### 📄 Description Slowly trying to make the release process easier. To start, I wrote a script+manually-triggered action which will automatically create a release PR for the "next" version and bump all `package.json` files to that version. If you don't specify a version, it infers it using this logic which to me seems to mirror how we already do releases (pseudocode): ```javascript if (day_of_month <= 25) { patchVersion++; } else { patchVersion = 0; minorVersion = next_month(); majorVersion = year_of_next_month(); } ``` See [this test run](https://github.com/jfdoming/actual/actions/runs/13171792952/job/36763370941) which generated https://github.com/jfdoming/actual/pull/5. I'm thinking eventually we can move the release note generation to this action as well and save an extra round trip with CI! It would also be nice to automatically generate the release docs. One day... --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:10:23 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#5311