Version updated for https://github.com/ToQuery/wails3-build-action to version v3-alpha.14. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary The GitHub Action automates the building of Wails.io applications using GoLang and NodeJS, providing options for customizing the build process, including obfuscation, platform support, caching, and artifact uploading. It supports building on macOS, Windows, and Linux, and can handle multiple platforms simultaneously.

Version updated for https://github.com/Verificate-Dev/verificate-gate-action to version v1.0.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary The Verificate Gate GitHub Action is designed to block pull requests that contain broken AI code, such as hallucinated APIs, mock/placeholder detections, or reward-gaming tests. It automates the process of checking every changed code file through a set of deterministic reality gates and fails the check on a veto, ensuring that only clean and reliable changes are allowed to merge into the repository. The action provides a clear and concise way to maintain quality in AI-driven projects by identifying potential issues early.

Version updated for https://github.com/vig-os/sync-issues-action to version v0.5.0. This action is used across all versions by 9 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This action synchronizes all issues and pull requests from a repository to markdown files, including comments and conversations, groups review threads with diff snippets when available, preserves original bodies, and includes metadata. It can be used to generate static documentation or backups of issues and pull requests.

Version updated for https://github.com/yaniv-golan/cowork-harness to version v1.20.0. This action is used across all versions by 0 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary The cowork-harness action is a scriptable, CI-friendly test harness that reproduces Claude Cowork’s observable runtime contract closely enough to test skills without the locked Desktop app. It creates a sandboxed environment, simulates the agent and its constraints (e.g., sealed filesystem, MCP-only cross-boundary), and can run tests in various fidelity tiers such as replay or live with different requirements like token-free or with real resources.

Version updated for https://github.com/zuke-build/zuke to version v1. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action is a small and explicit build automation tool that uses tagged template runs processes with sane defaults (throw on failure, capture output) and is injection-safe. It can generate GitHub Actions, GitLab CI, or Azure Pipelines YAML based on the provider specified in the configuration. The main purpose of this action is to automate code-based builds without relying on plugins or bespoke DSLs, providing a clean and refactor-safe approach to CI/CD workflows.

Version updated for https://github.com/postman-cs/postman-gcp-spec-discovery-action to version v1.2.4. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the process of discovering and exporting OpenAPI specifications from Google Cloud services, such as BigQuery, Cloud Functions, and Firestore, using Application Default Credentials or Workload Identity Federation. It helps developers integrate their GCP resources seamlessly into Postman for onboarding, reducing manual effort by automatically resolving service configurations based on labels or specific API IDs.

Version updated for https://github.com/postman-cs/postman-insights-onboarding-action to version v2.4.4. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the process of linking services discovered by Postman Insights to API Catalog workspaces and git repositories after deployment. It helps ensure that all discovered services are included in the organization’s catalog with detailed information such as a collection, repo link, and live telemetry. The action uses a human-user PMAK and session access token for authentication and validates these credentials before linking writes.

Version updated for https://github.com/postman-cs/postman-repo-sync-action to version v2.9.3. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the process of exporting Postman collections and environments into a repository and setting up CI, mock servers, and monitors around them. It solves the problem of ensuring that project assets are centralized and managed within the codebase, facilitating easier collaboration and deployment. The action provides capabilities to export projects, manage environments, and configure CI settings for integration with GitHub Actions.

Version updated for https://github.com/postman-cs/postman-resolve-service-token-action to version v2.1.1. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action automates the process of minting fresh service account access tokens and team IDs for use in Postman Onboarding workflows. It solves the problem of managing service account credentials securely by generating them directly from the CI environment, reducing the need to store sensitive information in repository secrets or personal access tokens (PMAKs). The key capabilities include:

Version updated for https://github.com/postman-cs/postman-smoke-flow-action to version v3.4.2. This publisher is shown as ‘verified’ by GitHub. This action is used across all versions by 0 repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action reshapes and organizes a Postman Smoke collection into an ordered journey using the specified flow path. It automatically derives or curates a manifest from the OpenAPI specification if none is provided, supports OAuth2 and API key authentication, and can handle concurrent runs through lease-based concurrency management. The action is part of the Postman API Onboarding suite and requires a Postman access token for execution.