github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[PR #7755] [MERGED] [AI] Fix publish-npm-packages workflow setup-node input #114183

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

📋 Pull Request Information

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

Base: master ← Head: matiss/fix-publish-npm-cache-input

📝 Commits (3)

  • e4c57a8 [AI] Fix publish-npm-packages workflow setup-node input
  • 1ef9619 Add release notes for PR #7755
  • 2be9816 Change category from Bugfixes to Maintenance

📊 Changes

2 files changed (+6 additions, -1 deletions)

View changed files

📝 .github/workflows/publish-npm-packages.yml (+0 -1)
➕ upcoming-release-notes/7755.md (+6 -0)

📄 Description

Summary

  • The cache input on actions/setup-node expects a package-manager string ('npm' / 'yarn' / 'pnpm'), not a boolean. Passing cache: false made the v26.5.1 release Publish npm packages job fail with Caching for 'false' is not supported (failed run).
  • Caching is disabled by default when the input is omitted, so this PR drops the line entirely in .github/workflows/publish-npm-packages.yml.

🤖 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/7755 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 5/8/2026 **Status:** ✅ Merged **Merged:** 5/8/2026 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `matiss/fix-publish-npm-cache-input` --- ### 📝 Commits (3) - [`e4c57a8`](https://github.com/actualbudget/actual/commit/e4c57a87eb3d186ee80bc6ea59175a3382b6e0fe) [AI] Fix publish-npm-packages workflow setup-node input - [`1ef9619`](https://github.com/actualbudget/actual/commit/1ef96190339087cd5292ae398b9b8b36c801037a) Add release notes for PR #7755 - [`2be9816`](https://github.com/actualbudget/actual/commit/2be981653a8b71976a19c8faf75366b6a6aba586) Change category from Bugfixes to Maintenance ### 📊 Changes **2 files changed** (+6 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/publish-npm-packages.yml` (+0 -1) ➕ `upcoming-release-notes/7755.md` (+6 -0) </details> ### 📄 Description ## Summary - The `cache` input on `actions/setup-node` expects a package-manager string (`'npm'` / `'yarn'` / `'pnpm'`), not a boolean. Passing `cache: false` made the v26.5.1 release `Publish npm packages` job fail with `Caching for 'false' is not supported` ([failed run](https://github.com/actualbudget/actual/actions/runs/25568669467/job/75058914839)). - Caching is disabled by default when the input is omitted, so this PR drops the line entirely in `.github/workflows/publish-npm-packages.yml`. 🤖 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-05 21:46:59 -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#114183
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?