github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 23:26:48 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[PR #8142] [MERGED] [AI] Drop ACTIONS_UPDATE_TOKEN from release workflows #122361

New Issue
Closed
opened 2026-06-11 21:12:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-11 21:12:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/8142
Author: @MatissJanis
Created: 6/7/2026
Status: ✅ Merged
Merged: 6/8/2026
Merged by: @MatissJanis

Base: master ← Head: drop-actions-update-token

📝 Commits (3)

  • 34babb8 [AI] Drop ACTIONS_UPDATE_TOKEN from release workflows
  • b9c6b0a [AI] Add release note for ACTIONS_UPDATE_TOKEN removal
  • 7c4683e Update 8142.md

📊 Changes

3 files changed (+18 additions, -9 deletions)

View changed files

📝 .github/workflows/cut-release-branch.yml (+2 -6)
📝 .github/workflows/release-notes.yml (+10 -3)
➕ upcoming-release-notes/8142.md (+6 -0)

📄 Description

Description

Removing ACTIONS_UPDATE_TOKEN env var usage from a few workflows. I don't think it is necessary anymore; we can find a different solution to achieve the same.

Spoilers: I have not fully tested this (testing gh actions is a pain..), but I think it should work.

Related issue(s)

N/A

Testing

N/A

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

🤖 Generated with Claude Code

🔄 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/8142 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 6/7/2026 **Status:** ✅ Merged **Merged:** 6/8/2026 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `drop-actions-update-token` --- ### 📝 Commits (3) - [`34babb8`](https://github.com/actualbudget/actual/commit/34babb849aa78e0d1553390dd3a3296499a18c16) [AI] Drop ACTIONS_UPDATE_TOKEN from release workflows - [`b9c6b0a`](https://github.com/actualbudget/actual/commit/b9c6b0a008dc3360665641d87f7cc6fd71059cef) [AI] Add release note for ACTIONS_UPDATE_TOKEN removal - [`7c4683e`](https://github.com/actualbudget/actual/commit/7c4683ef7934aee9b4f105e5a25ef6de907994fd) Update 8142.md ### 📊 Changes **3 files changed** (+18 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/cut-release-branch.yml` (+2 -6) 📝 `.github/workflows/release-notes.yml` (+10 -3) ➕ `upcoming-release-notes/8142.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?--> Removing `ACTIONS_UPDATE_TOKEN` env var usage from a few workflows. I don't think it is necessary anymore; we can find a different solution to achieve the same. Spoilers: I have not fully tested this (testing gh actions is a pain..), but I _think_ it should work. ## Related issue(s) <!-- e.g. Fixes #123, Relates to #456 --> N/A ## Testing <!-- What did you test? How can we reproduce the issue you are fixing or how can we test the feature you built? --> N/A ## 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 ---> 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <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-06-11 21:12:07 -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
tech-support
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#122361
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?