Repository navigation
Releases
Release 1.16.0-beta.1
Adds Action Usage, a page that shows which actions your managed workflows use and updates them to the latest release, and makes every pull request campaign closable.
New
- Action Usage. A fourth tab in the app header lists every action your managed workflows use, at which version, and in how many workflows and repositories. It flags each reference that isn't pinned to a full commit SHA, the ones that would fail under an organization SHA-pinning policy, and can filter down to just those.
- Update actions to the latest release. Opening an action on Action Usage looks up its latest release. Each workflow that isn't on it gets an Update button with two choices: Update and review opens the workflow in the editor with the new version, saving nothing until you commit, and Update and commit locally saves it in the project straight away. Update all updates every workflow that uses the action, and Change lets you pick a tag, branch or commit instead. Neither choice opens a pull request; deliver the change with the project's Create Pull Requests as usual.
Fixed
- Every campaign can now be closed. A pull request opened by a linked project can be merged or closed from either project's campaigns tab, provided you can edit the project that opened it.
- Pull requests GitHub no longer has. A pull request whose repository or pull request was deleted on GitHub is marked Not found on GitHub and can be removed from its campaign. Remove appears as soon as a close finds it gone, so the campaign no longer stays open forever.
Changed
- The default AM Build Vars action is now seeded from
greywolflabs/am-build-vars, where the repository has moved. Installs that already have it keep theirdawg-io/am-build-varsentry, which GitHub redirects to the new location, and don't get a second copy.
Improved
- The documentation screenshots, the README animation and the product demo video show the new four-tab header, and the narrated demo on YouTube has been re-recorded.
- Dependency and security updates across the frontend, backend and documentation site.
Release 1.15.0-beta.1
Adds a Managed Files section (CODEOWNERS first), one drift list with the same two fixes for every file, and a new app header and Projects page.
New
- Managed Files. A new section for repository files that belong to the whole repository rather than to a workflow. CODEOWNERS is the first file kind. Each project manages one file kind for a group of repositories, and each repository can be in one project per file kind. The self-hosted beta allows 3 Managed Files projects.
- One header on every page. Projects, Managed Files and Managed Actions are now peer tabs in a single header that stays at the top while you scroll, with the account menu and your plan name beside it.
- A redesigned Projects page. Project cards show their state and drift at a glance, the grid ends with a dashed "New project" box that shows how many projects your plan has room for, and a slim usage meter sits beside the New Project button.
- One drift list, the same two fixes for every file. Workflows, custom files and CODEOWNERS now share one drift list. Keep ActionsManager Version opens a pull request campaign for the drifted repositories, and Use GitHub Version makes GitHub's copy the project's version. Every change to GitHub goes through a pull request.
- Sidebar collapse toggle. The strip across the top of the sidebar is now the collapse control, with a soft glow, one chevron and reduced-motion support.
Fixed
- Two projects that shared a repository no longer overwrite each other's CODEOWNERS file or report each other's change as drift.
Changed — read before upgrading
- CODEOWNERS is now managed only in Managed Files. Caller and Reusable Workflow Projects can no longer save or import a CODEOWNERS file.
- Upgrading removes the CODEOWNERS files, and any custom file at a path GitHub reads CODEOWNERS from, that workflow projects stored in ActionsManager, along with their delivery and drift records. Files in your repositories are not touched. To keep managing one, create a CODEOWNERS project for those repositories and load the file from one of them.
- A CODEOWNERS change that was committed locally but never delivered exists only in ActionsManager, so upgrading loses it. Deliver it, or copy it, first.
Improved
- The documentation screenshots, the README animation and the product demo video show the new layout, and the example project is now NodeBuilds.
- Dependency and security updates across the frontend, backend and documentation site.
Release 1.14.0-beta.2
Apache-2.0 licensing that GitHub recognises, a shorter README with demo videos, a bug report form with questions and ideas moved to Discussions, and a fix for the Create PR Campaign dialog.
Before you upgrade
install.shhas been removed. Start ActionsManager with thedocker runcommand in the README, or with Docker Compose as described inINSTALLATION.md. A savedcurl … install.sh | bashcommand will stop working. Containers you already installed with it are not affected.
New
- Bug report form. New issues use a form that asks for your ActionsManager version, how you run it, and confirmation that tokens and secrets were removed. Questions go to Discussions → Q&A, feature ideas to Discussions → Ideas, and security problems can be reported privately.
- Demo videos. The README shows a PR campaign rolling one workflow out to three repositories, and the docs home page plays it as video. The Product Demo page has the full walkthrough, from sign-in to merge, and a narrated version with captions is on YouTube: https://youtu.be/8TrgE9YDGXA
Fixed
- Create PR Campaign dialog. The preflight explanation now appears only for projects that use a validation repository, and the "campaign creation is locked" note only while creation actually is locked.
- Dialog headers in light mode. With your operating system in light mode, the Create PR Campaign and Import Existing dialogs had a near-white header and footer that hid their titles. They're now dark, like the rest of the app.
- License detection.
LICENSEis now the standard Apache License 2.0 text, so GitHub identifies the project as Apache-2.0. A newNOTICEfile credits GreyWolf Labs. The container image includes both, in/app.
Improved
- Documentation.
- The README is shorter: what ActionsManager does, a quick start, how it compares with similar tools, and links into the docs.
- The docs no longer mention paid plans or a license that may change.
LICENSE_KEYis optional and the beta doesn't use it. - The docs no longer describe direct commit as a way to deliver a workflow, because every change goes out as a pull request. Direct commits remain only where you choose them: Restore Directly, or adopt and sync, when resolving drift, and removing a file.
- Contributing. Fork
greywolflabs/actions-managerand open pull requests against thestagingbranch.
Release 1.14.0-beta.1
Delete a project together with its files in GitHub, drift checking for every file a project delivers, one CODEOWNERS file per project, and identity taken from your sign-in session everywhere.
Before you upgrade
- Back up first. This release changes how ActionsManager records what it delivered to each repository and branch, and moves your existing records over when it starts.
- CODEOWNERS is now one file per project. A project that kept a different CODEOWNERS in each repository keeps the most recently edited one. Its next PR Campaign delivers that file to every repository in the campaign. The Target Repositories checkboxes are gone.
- API changes for scripts:
POST /api/update-workflowis nowPOST /api/update-project-files. The old path is gone.POST /api/sync-workflow,GET /api/workflow-statusand other routes the app no longer used have been removed.- Every route now acts as the signed-in user. A
github_useroruservalue in the request no longer chooses who the request acts as.
New
- Delete a project with its files. When you delete a project, you choose what happens to its files in GitHub:
- Keep the files: the project is deleted at once and nothing in GitHub changes.
- Remove the files: a PR Campaign opens one pull request per repository and branch, removing each file where it was delivered. The project shows as Deleting and is read-only while they're open. It's deleted when they all merge, and the deletion is called off if one is closed.
- Secrets and variables are a separate choice, and are deleted straight away.
- Custom files are checked for drift. A custom file changed or deleted in GitHub now shows as drift in Project Files and the drift banner.
- CODEOWNERS drift shows everywhere workflow drift does: the drift banner, Review Drift, the Projects list, notifications and Project Files.
- Edit files that are under review. Custom files and CODEOWNERS can now be unlocked while their pull request is open, like workflows. Commit and Update PR saves the change and pushes it to that pull request. A locked file shows a greyed-out Commit Locally.
- The trigger decides whether a workflow is reusable. Adding
workflow_callmakes a workflow reusable, and removing it makes it a regular workflow again. - GUI editor: a workflow the GUI can't edit without losing something stays in YAML, and the editor names the parts it can't represent. Schedules, step ids and jobs that call a reusable workflow now survive GUI edits, and a workflow no longer needs a
name:. - Token status: the user menu now says when a token has no repository access, is blocked by an organization policy, or couldn't be checked, instead of calling every saved token Configured. A saved token that can't be decrypted shows Saved but unreadable.
Fixed
- Drift:
- Workflows, CODEOWNERS and custom files are now judged by one rule, against a record of what was delivered to each repository and branch. This fixes:
- local edits reported as drift;
- real changes in GitHub hidden by a local edit;
- repositories a file was never delivered to reported as drifted;
- an open pull request to one branch hiding drift on the repository's other branches.
- Commit Locally on a drifted workflow or CODEOWNERS clears its drift straight away, without waiting for the next check.
- Use GitHub version and adopt-and-sync now use the branches the project delivers to, not the repository's default branch. A failure on one repository no longer stops the rest.
- Background drift checks no longer stall behind projects that can't be checked.
- The workflow editor no longer says "No drift detected" just because a workflow is synced.
- A Caller Workflow Project's own reusable workflows are drift-checked where they're delivered, and can be removed from their repositories.
- Workflows, CODEOWNERS and custom files are now judged by one rule, against a record of what was delivered to each repository and branch. This fixes:
- Renames, moves and deletions remove the file where it was actually delivered, on every branch it was delivered to. A file renamed and then deleted before the rename was delivered is removed under its old name.
- Pull requests: after one campaign pull request was closed without merging, later merges left files at "Committed locally". The Merge button, the GitHub webhook and a refresh now all record a merge the same way.
- Save and push writes only to the project's own repositories and applies the project's name prefix.
- Projects:
- Creating a project with a name you already use is refused, instead of quietly changing your existing project. Renaming a project to one is refused too.
- Two owners' projects with the same name are no longer mixed up. Project pages act on their own project, and names containing
_or%match literally. - A member who created a project can now edit it, instead of seeing it read-only.
- Permissions:
- Read-only members can no longer see secret and variable names, counts or run status for projects they have no access to.
- Anyone with edit access to a project can sync, apply and remove its rulesets, not only the person who added them.
- Environment variable and environment changes are limited to the project's own repositories, and names are validated before anything is sent to GitHub.
- Rulesets: a ruleset uploaded without a name is applied under its listed name, so sync status finds it. Invalid input gets a clear error instead of a server error, and an uploaded ruleset always attaches to its project.
- Error messages no longer include internal details such as database queries or host names.
- PostgreSQL: on a database server not set to UTC, times were stored in local time. Every session now runs in UTC. Times stored before this version aren't converted.
Improved
- Performance: project lists and background drift checks use new indexes and a stored next-check time.
- Dependencies: frontend, backend and build tooling updates, including Tailwind CSS 4, with no change to the interface.
- Documentation:
- pages updated for this release's drift, delivery and permission rules;
- a new section on editing files whose pull request is still open;
- a caution about restoring older backups;
- the outdated direct-commit delivery guides removed.
Known issues
- Back up before upgrading. If an upgrade stops partway through, restore that backup before you try again, rather than starting the upgrade again.
- Restoring a backup taken before this version isn't supported. It can fail if a project had CODEOWNERS in more than one repository.
- Sync each project's CODEOWNERS once after upgrading. Until you do, changes made to CODEOWNERS in GitHub aren't reported as drift.
- A rename waiting at upgrade time can leave the old file behind. If a workflow or custom file was renamed but not yet delivered when you upgrade, its old copy can stay in the repository. Delete it by hand.
- A new file at a renamed file's old path can be removed. If you rename or move a file, then create a new file at its old path, a later delivery of the renamed file can delete the new one. Check the deletions in campaign pull requests before merging.
- A failed removal of an old copy isn't retried. If removing the old copy of a renamed file fails, it stays in the repository and isn't cleaned up later. Delete it by hand.
Initial release: ActionsManager Self-Hosted Beta 1.13.0-beta.1
Stricter sign-in and project permissions, a self-hosted image built and verified in this repository, drift status you can rely on, and a refreshed documentation site.
Before you upgrade
-
The self-hosted image has moved to
ghcr.io/greywolflabs/actions-manager. It is built from this repository's release tag, and it is tagged only after it passes:- a smoke test
- a version check
- a vulnerability scan
An existing install that pulls
ghcr.io/dawg-io/actions-managerwon't receive this release or later ones. Update your copy ofdocker-compose.self-hosted.yml, or setACTIONS_MANAGER_IMAGE=ghcr.io/greywolflabs/actions-manager:latest. -
Token sign-in now accepts only personal access tokens, either classic (
ghp_…) or fine-grained (github_pat_…).- These tokens are refused, with an explanation:
- OAuth tokens, including the output of
gh auth token - GitHub App user tokens
- installation tokens
- OAuth tokens, including the output of
- Existing sessions keep working until they expire.
- These tokens are refused, with an explanation:
Fixed
- Permission checks: several cross-project permission gaps are closed.
- Updating a workflow and deleting a custom file now require editor access to the project.
- The extended project-delete action checks that you own the project.
- Environment-variable changes apply only to the project you have write access to.
- The reusable-workflow list always reflects the signed-in user.
- First-boot restore refuses a backup that contains no workspace members.
- Secret values are no longer written to logs or the browser console.
- Drift status:
- Restarting or upgrading no longer marks clean projects as needing attention.
- The project's drift status row now agrees with the Projects list. A check that couldn't reach every repository says so, and is never shown as "No drift detected".
- GitHub webhooks: deliveries to
/webhooks/githubnow reach the app in the self-hosted image. - PostgreSQL: installs could fail to start with "No module named psycopg". Fixed.
- Workflow updates: a refused workflow update now shows an error instead of appearing to succeed.
- Fonts: pages no longer fall back to a serif font on systems without the preferred fonts.
- Installer: the OAuth settings and
SECRET_KEYare now written to.env.self-hosted.
Changed
- Repository limit: the repositories-per-project limit now also applies when you add repositories to an existing project. A project already over the limit can still be edited, renamed and trimmed.
- Private repositories: they now appear in the repository pickers on every self-hosted install, matching the private-repository projects these installs already allowed.
- Plan wording: plan and limit text in the app now comes from the server, and the installer links to the beta limits instead of listing paid tiers.
- Sign-in screen: it waits for the server before offering token sign-in, and keeps retrying while the container starts.
Improved
- Container: nothing in the self-hosted container runs as root after its data directory is prepared.
- Documentation:
- a new home page and refreshed screenshots
- the demo video loads only when you press play
- only the self-hosted beta limits are stated
- backup and restore commands updated for the non-root container
- Dependencies: patch and minor dependency updates across the frontend, backend and build tooling.