Skip to content

Chore/actions cleanup - #134

Merged
deepagent-ai merged 3 commits into
devfrom
chore/actions-cleanup
Sep 27, 2026
Merged

deepagent-ai merged 3 commits into
devfrom
chore/actions-cleanup

Conversation

@deepagent-ai

Copy link
Copy Markdown
Contributor

Issue for this PR

Closes #

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Please provide a description of the issue, the changes you made to fix it, and why they work. It is expected that you understand why your changes work and if you do not understand why at least say as much so a maintainer knows how much to value the PR.

If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!

How did you verify your code works?

Screenshots / recordings

If this is a UI change, please include a screenshot or recording.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

…file

The desktop node-bundle guard (script/build-node.ts) fails the build on any
Bun-only runtime API reachable from the sidecar bundle — the origin-file
rewrite from the MCP secret migration used Bun.file, which is fine in the
Bun CLI but broke the desktop build on every platform once merged (all
desktop-build matrix jobs failed at the renderer build step with
"Node server bundle contains Bun-only runtime APIs: Bun.file").

Swap to the Filesystem wrapper (node:fs) the CLI already uses for config
file IO. Verified locally with the same build-node.ts guard, package
typecheck, and the MCP secret migration tests (11/11).
The actions list was dominated by non-build noise: hourly/daily schedules
(beta, compliance-close every 30 minutes, docs-update, stats, close-issues,
close-prs), PR hygiene bots (pr-routing, pr-standards, pr-management,
duplicate-issues), and push-to-dev fan-out firing ~10 workflows per merge.

Build and CI workflows (publish, desktop-build, test, typecheck, branding,
generate, storybook, nix-*, containers, deploy, docs-locale-sync,
release-github-action) now trigger only on push to main — i.e. the dev->main
merge — plus manual dispatch. Scheduled and PR-bot workflows keep manual
workflow_dispatch only. Untouched: comment-triggered agent workflows (they
only run when explicitly invoked), release-event notify, and tag-publishers.

Note: PRs no longer run test/typecheck checks; verification happens at the
dev->main merge instead.
@github-actions

Copy link
Copy Markdown

Hey! Your PR title Chore/actions cleanup doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, deepagent-code).

See CONTRIBUTING.md for details.

@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • No "Type of change" checkbox is checked. Please select at least one.
  • No issue referenced. Please add Closes #<number> linking to the relevant issue.
  • "How did you verify your code works?" section is empty. Please explain how you tested.
  • Not all checklist items are checked. Please confirm you have tested locally and have not included unrelated changes.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@deepagent-ai
deepagent-ai merged commit 73add6e into dev Sep 27, 2026
4 checks passed
@deepagent-ai
deepagent-ai deleted the chore/actions-cleanup branch September 27, 2026 17:26
deepagent-ai added a commit that referenced this pull request Sep 27, 2026
lxrzlyr pushed a commit that referenced this pull request Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant