Releases: kelos-dev/open-actions
Releases · kelos-dev/open-actions
Release list
v0.1.0
API Changes
- Ordinary pull request workflows can now run for fork and Dependabot contributions with configurable approval, token, and secret policies. Same-repository Dependabot pull request workflows are approval-gated by default and always use read-only tokens without Project secrets. (#121, @gjkim42)
- Open Actions now supports job-level concurrency groups, and workflow and job
cancel-in-progresspolicies can use expressions. (#104, @gjkim42) - Runner execution profiles can configure the runner image pull policy and workflow Pod termination grace period. When
spec.execution.terminationGracePeriodSecondsis omitted, workflow Pods use the Kubernetes 30-second default instead of a controller-provided 300 seconds. (#105, @gjkim42) - Add RunnerSet resources for managing replicated Runner execution capacity. (#108, @gjkim42)
- Workflow steps now support
continue-on-errorwith Boolean and expression values, including GitHub-compatible step outcome and conclusion semantics. (#100, @gjkim42) - Allow workflows to assign non-default
GITHUB_andRUNNER_environment variables, includingGITHUB_TOKEN, while preserving GitHub Actions-compatible protection for runner-owned values. (#103, @gjkim42) - Workflow jobs can derive matrix configurations from dependency outputs, including JSON matrices evaluated with
fromJSON. (#95, @gjkim42) - Workflow steps can use direct dependency results and outputs through the needs context. (#101, @gjkim42)
- Expose stable workflow run identity and attempt metadata, Console run URLs, and a supported stale-run query to Open Actions workflows. (#94, @gjkim42)
- Workflow jobs now support
timeout-minutes, capped by the cluster-widecontroller.maxJobTimeoutsetting, with distinct timed-out status and bounded cleanup execution. (#96, @gjkim42) - Support workflow-level environment variables with workflow, job, and step precedence. (#91, @gjkim42)
- Open Actions constructs ordinary pull request integration revisions locally instead of waiting for GitHub test merge refs. For these runs, github.sha identifies the local integration commit; use actions/checkout to materialize it and a pull request parent SHA for services that require a GitHub-hosted commit. (#77, @gjkim42)
- Trusted fork workflows can validate an explicitly checked-out merge commit against the pinned base and pull request head revisions before executing it. (#72, @gjkim42)
- Projects can provide Kubernetes-backed workflow secrets and variables, and Console administrators can manage Project Secret values from the authenticated Projects page. (#64, @gjkim42)
- GitHub Check Run rerequests now create a new Open Actions WorkflowRun attempt that reruns failed jobs and their dependent graph while updating the original check. (#70, @gjkim42)
- Matrix jobs now support strategy.fail-fast, defaulting to true, to stop unfinished combinations after a sibling fails. (#69, @gjkim42)
- Open Actions now schedules workflow jobs as dependency graphs and supports job conditions, skipped and cancelled results, dependency outputs, matrix result aggregation, and cancellation-aware cleanup jobs. (#56, @gjkim42)
- Workflow steps and jobs can publish outputs through GITHUB_OUTPUT, and completed job outputs are persisted on WorkflowJob status. (#55, @gjkim42)
- Workflows can expand scalar matrix strategies, use matrix values in runner selection and job expressions, and limit matrix concurrency with
max-parallel. (#54, @gjkim42) - Open Actions recognizes the remaining Kelos workflow triggers and can initiate webhook, manual, scheduled, chained, and reusable workflow runs. (#47, @gjkim42)
- Runners can optionally provide a job-scoped Docker daemon for Docker-dependent steps and Node actions such as helm/kind-action. (#53, @gjkim42)
- Fix pull request check links by associating GitHub Check Runs with the pull request head commit. (#49, @gjkim42)
- WorkflowRuns can set
spec.ttlSecondsAfterFinishedto automatically delete completed runs and their owned resources. (#42, @gjkim42) - Workflow resources now use readable names based on workflow filenames and job IDs, and WorkflowJobs expose authored job names. (#16, @gjkim42)
Features
- Tagged releases now publish cross-platform Open Actions CLI binaries and a versioned Helm chart. (#126, @gjkim42)
- The Console now displays the exact workflow file used by each workflow run. (#125, @gjkim42)
- The standard runner image now uses a minimal Ubuntu 24.04 base. Tools previously inherited from Debian buildpack-deps, including GCC, G++, wget, OpenSSH client, unzip, xz-utils, bzip2, patch, file, and procps, are no longer included; workflows that require them must install them in a custom runner image. A CI-validated custom runner example is included. (#124, @gjkim42)
- Allow controller, artifact server, and Console resource requests and limits to be configured during installation. (#123, @gjkim42)
- Open Actions reduces GitHub API traffic by reusing control-plane installation tokens, honoring rate-limit cooldowns, and skipping unnecessary action-download tokens. (#122, @gjkim42)
- Open Actions now honors workflow- and job-level permissions when creating the job-scoped GitHub token. (#107, @gjkim42)
- Workflows can upload and download retained artifacts with supported versions of actions/upload-artifact and actions/download-artifact. (#98, @gjkim42)
- Console administrators can gracefully cancel active workflow runs. (#99, @gjkim42)
- GitHub workflows now receive the complete authenticated event payload through github.event and GITHUB_EVENT_PATH. (#93, @gjkim42)
- Administrators can now trigger workflow_dispatch runs from the Open Actions Console. (#92, @gjkim42)
- Console administrators can rerun all jobs or only failed jobs from completed workflows. (#89, @gjkim42)
- The Console now serves workflow, Project, and runner log pages without authentication. Project Secret changes still require administrator sign-in. (#78, @gjkim42)
- Open Actions now supports endsWith, join, toJSON, fromJSON, hashFiles, and object-filter wildcards in workflow expressions. (#74, @gjkim42)
- Workflow step headings in the Console now show whether each step is running, succeeded, failed, or cancelled. (#61, @gjkim42)
- Successful workflow steps in the Console now collapse automatically when they complete. (#58, @gjkim42)
- The Open Actions Console now provides a main view listing recent workflow runs across all namespaces. (#52, @gjkim42)
- Workflow logs now use a GitHub Actions-style interface with grouped steps, debug filtering, source annotations, and secret-safe action metadata. (#43, @gjkim42)
- Open Actions now evaluates GitHub Actions expressions during workflow planning and step execution. (#45, @gjkim42)
- Open Actions runners can execute JavaScript actions that declare the Node 24 runtime. (#44, @gjkim42)
- Add GitHub Check Run reporting and an authenticated Open Actions Console for workflow status and live logs. (#18, @gjkim42)
Bug Fixes
- Failed-job reruns now reuse completed prerequisite results and outputs instead of rerunning successful prerequisite jobs. (#127, @gjkim42)
- Console log line numbers remain on one line when a job produces 1,000 or more log entries. (#106, @gjkim42)
- Improve Console responsiveness when viewing long runner logs. (#90, @gjkim42)
- Authenticate external actions from repositories available to the Project's GitHub App installation. (#79, @gjkim42)
- Prevent pull request workflows from failing during checkout when credentials are persisted. (#80, @gjkim42)
- Controller failures are now reported as Kubernetes Warning Events on affected Projects, Runners, WorkflowRuns, and WorkflowJobs. (#73, @gjkim42)
- Improved Console navigation spacing between the Open Actions brand and Projects link. (#71, @gjkim42)
- Console log streams no longer duplicate existing output after reconnecting. (#57, @gjkim42)
- The Open Actions console now renders ANSI colors and text styles in workflow logs instead of displaying raw escape sequences. (#62, @gjkim42)
- Fixed Console runner log rows wrapping incorrectly when timestamps are enabled. (#59, @gjkim42)