github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-21 06:31:58 -05:00
Code Issues 2.1k Packages Projects Releases 57 Wiki Activity

[PR #7844] split release into two branches #77416

New Issue
Open
opened 2026-05-16 19:18:32 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-16 19:18:32 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/7844
Author: @matt-fidd
Created: 5/14/2026
Status: 🔄 Open

Base: master ← Head: release-automation/split-branches

📝 Commits (7)

📊 Changes

8 files changed (+207 additions, -110 deletions)

View changed files

📝 .github/actions/docs-spelling/expect.txt (+1 -0)
📝 .github/actions/release-notes/generate/action.yml (+14 -0)
📝 .github/workflows/cut-release-branch.yml (+79 -39)
📝 .github/workflows/release-notes.yml (+35 -9)
📝 packages/ci-actions/bin/get-next-package-version.ts (+12 -0)
📝 packages/ci-actions/bin/release-notes-generate.mjs (+38 -18)
📝 packages/docs/docs/contributing/releasing.md (+22 -44)
➕ upcoming-release-notes/7844.md (+6 -0)

📄 Description

Description

AI disclaimer: Claude helped out with some of this, but it's been checked over thoroughly and the docs were written by my own fair hands

There were some teething issues with the new release process last month, here's the PR that hopefully fixes the main one!

The release process is detailed in the docs, but the high level is:

  • long lived release branch that survives between releases, all tags live here
  • cut generates a release-specific branch to hold the bumps and docs changes
  • cherry picks on the release branch trigger release note generation in the release-specific branch

TODOs for later PRs:

  • Release candidate docker/npm publishing
  • Rework how the default dates are calculated
  • Fix not being able to rename blog post by date

Related issue(s)

Testing

Tested on my fork, see https://github.com/matt-fidd/actual/pull/21

Checklist

  • Release notes added (see link above)
  • No obvious regressions in affected areas
  • Self-review has been performed - I understand what each change in the code does and why it is needed

🔄 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/7844 **Author:** [@matt-fidd](https://github.com/matt-fidd) **Created:** 5/14/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `release-automation/split-branches` --- ### 📝 Commits (7) - [`07e9ad3`](https://github.com/actualbudget/actual/commit/07e9ad31706284b447c9a07e4b9e46a19f7eebb5) split release into two branches - [`1616ccb`](https://github.com/actualbudget/actual/commit/1616ccbb388a5ec1c4ad4b9b47e4f8006397bc51) update docs to match the new process - [`acbc02d`](https://github.com/actualbudget/actual/commit/acbc02d4e0312c36e56db47239134cbfc0e4beb3) note - [`e4474a9`](https://github.com/actualbudget/actual/commit/e4474a9f1e46ab5f7e448797c04f5505126b6d73) zizmor comment - [`c074bfe`](https://github.com/actualbudget/actual/commit/c074bfec961431c0785568cee3d8876b46305b16) Update check-spelling metadata - [`79d97f5`](https://github.com/actualbudget/actual/commit/79d97f54a681820365bb6712e94ae50684a6bde5) use single long lived release branch - [`462b269`](https://github.com/actualbudget/actual/commit/462b2692583aafb85ccdc0edbf8346702f66b7c5) coderabbit ### 📊 Changes **8 files changed** (+207 additions, -110 deletions) <details> <summary>View changed files</summary> 📝 `.github/actions/docs-spelling/expect.txt` (+1 -0) 📝 `.github/actions/release-notes/generate/action.yml` (+14 -0) 📝 `.github/workflows/cut-release-branch.yml` (+79 -39) 📝 `.github/workflows/release-notes.yml` (+35 -9) 📝 `packages/ci-actions/bin/get-next-package-version.ts` (+12 -0) 📝 `packages/ci-actions/bin/release-notes-generate.mjs` (+38 -18) 📝 `packages/docs/docs/contributing/releasing.md` (+22 -44) ➕ `upcoming-release-notes/7844.md` (+6 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://actualbudget.org/docs/contributing/#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> ## Description <!-- What does this PR do? Why is it needed? Please give context on the "why?": why do we need this change? What problem is it solving for you?--> AI disclaimer: Claude helped out with some of this, but it's been checked over thoroughly and the docs were written by my own fair hands There were some teething issues with the new release process last month, here's the PR that hopefully fixes the main one! The release process is detailed in the docs, but the high level is: - long lived release branch that survives between releases, all tags live here - cut generates a release-specific branch to hold the bumps and docs changes - cherry picks on the release branch trigger release note generation in the release-specific branch TODOs for later PRs: - Release candidate docker/npm publishing - Rework how the default dates are calculated - Fix not being able to rename blog post by date ## Related issue(s) <!-- e.g. Fixes #123, Relates to #456 --> ## Testing <!-- What did you test? How can we reproduce the issue you are fixing or how can we test the feature you built? --> Tested on my fork, see https://github.com/matt-fidd/actual/pull/21 ## Checklist - [x] Release notes added (see link above) - [x] No obvious regressions in affected areas - [x] Self-review has been performed - I understand what each change in the code does and why it is needed <!--- actual-bot-sections ---> --- <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-05-16 19:18:32 -05: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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#77416
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?