Version updated for https://github.com/rtwsvj/skill-switch to version v0.9.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. What’s Changed 安装 / Install macOS(Apple Silicon)桌面 App:下载下方 skill-switch_0.9.0_aarch64.dmg(29M,Developer ID 签名 + Apple 公证),拖进「应用程序」即可。 SHA-256: d415f3b1346de71c57b1e537e3da961c9cc9d19d375f743af7bc15e1adc7c0fd CLI:npx @rtwsvj/skill-switch audit [0.9.0] - 2026-07-01 自 v0.6.0(npm 上最后一个已发布版本)以来累积的所有内容一次发布:含原 0.7 / 0.8 批次 + 第三波(RE2/shadcn/bun)+ 第四波「集众家之所长」+ SkillsMP 源 + GUI 各屏 shadcn 迁移。

Version updated for https://github.com/siiway/verified_bot_commit to version v0.2.0. This action is used across all versions by 3 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Full Changelog: https://github.com/siiway/verified_bot_commit/compare/v0.1.1...v0.2.0

Version updated for https://github.com/skaldlab/muninn to version v0.3.4. This action is used across all versions by 1 repositories. Action Type This is a Docker action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Changelog [0.3.4] - 2026-07-04 Changed Docker image scanner updates: osv-scanner 2.4.0, trivy 0.72.0, semgrep 1.168.0, zizmor 1.26.1 (checkov remains at 3.2.531 pending aiohttp cap lift). [0.3.3] - 2026-06-17 Changed Trivy default severity is now all levels (UNKNOWN through CRITICAL) instead of CRITICAL and HIGH only. osv-scanner and trivy now overlap on medium/low advisories by default so cross-scanner dedup and Detected by work without extra config. Consumers can narrow the Trivy scan with scanners.trivy.severity; fail-on still controls which findings fail the run. [0.3.2] - 2026-06-16 Fixed Suppressions with tool and/or rule-id are now applied. Previously only id (path substring) and fingerprint matchers worked; tool+rule-id entries parsed from muninn.yml but silently no-op’d. [0.3.1] - 2026-06-16 Fixed Poutine v1.x JSON parsing: findings from poutine 1.1.6+ (rule_id, meta, rules, blobshas) now populate title, rule, and file in PR comments instead of empty shells (File: :0, `Rule: ``) (#41). Actionlint PR comments: fall back to kind (e.g. expression) when rule.name is absent; omit empty Rule lines. Poutine injection findings: render injection_sources as formatted Sources instead of plain meta.details text. Changed PR comment layout: shared field helpers; non-dependency findings follow File → Rule → optional extras → description; single-scanner dependency findings use File instead of a redundant Source line. [0.3.0] - 2026-06-16 Added Cross-scanner deduplication by advisory id: findings that report the same CVE/GHSA for the same package from different scanners (e.g. OSV-Scanner from a lockfile and Trivy from a container layer) are now collapsed into a single finding. The contributing scanners are recorded in a new detected_by field (surfaced in the JSON report, the PR comment’s “Detected by” line, and a detectedBy SARIF result property). A CVE is preferred over GHSA so the same vulnerability converges on one id across scanners (#27). Richer dependency finding rendering: aggregated dependency findings now appear under a neutral [dependency] heading (instead of a single scanner’s name) with Package, Advisory (including the shared CVE), Detected by, and a Sources list showing where each scanner observed it. A new sources field on the finding (per-scanner tool + file) backs the JSON report (#27). Fixed PR comment rendering: scanner descriptions are flattened to a single line and their Markdown (code fences, headings) neutralized, so an unbalanced ``` fence can no longer swallow later findings and the footer into a code block. [0.2.0] - 2026-06-15 Supply-chain hardening for the scanner image and signed, verifiable releases (closes #30).

Version updated for https://github.com/svierk/sfdx-run-tests to version v0.0.2. This action is used across all versions by 1 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed await flow test results via flow get test polling Full Changelog: https://github.com/svierk/sfdx-run-tests/compare/v0.0.1...v0.0.2

Version updated for https://github.com/vanducng/miu-cr to version v0.85.2. 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. What’s Changed miu-cr v0.85.2 AI code review for local changes and GitHub pull requests. Use it as a CLI, CI gate, or GitHub Action with your own LLM key. Install curl -fsSL https://cr.miu.sh/install.sh | sh -s -- v0.85.2 brew install vanducng/tap/miucr go install github.com/vanducng/miu-cr/cmd/miucr@v0.85.2 GitHub Action:

Version updated for https://github.com/WPTechnix/action-php-scoper to version v1.0.0. This action is used across all versions by ? repositories. Action Type This is a Docker action. Go to the GitHub Marketplace to find the latest changes. What’s Changed v1.0.0 — Initial Release A GitHub Action that runs PHP-Scoper to prefix PHP namespaces, preventing dependency conflicts when distributing PHP code as PHARs, WordPress plugins, or Composer libraries. Features Docker-based action built on humbugphp/php-scoper:0.18.19 with Composer 2 baked in Automatic dependency installation — runs composer install before scoping (configurable) 5 configurable inputs: working-directory, scoper-config, run-composer-install, composer-args, output-directory Graceful fallbacks when scoper.inc.php or composer.json are missing 2 outputs: output-path (absolute path to scoped files) and count-scoped (file count) Proper CI/CD annotations — uses ::error:: and ::warning:: for clear workflow logs Dependabot integration for automated Docker/Actions dependency updates What It Solves PHP distributable code (plugins, libraries, PHARs) often bundles third-party dependencies that can clash with the same dependencies loaded by the host application. This action automates PHP-Scoper’s namespace prefixing so every build produces isolated, conflict-free code.

Version updated for https://github.com/WPTechnix/wp-pot-generator to version v1.0.0. This action is used across all versions by ? repositories. Action Type This is a Docker action. Go to the GitHub Marketplace to find the latest changes. What’s Changed v1.0.0 – Initial Release First public release of WP POT Generator, a GitHub Action for generating WordPress .pot translation files using WP-CLI inside a Docker container. ✨ Features Generate .pot files for WordPress plugins and themes Powered by wp i18n make-pot running in Docker Automatic detection of plugin/theme slug Automatic detection of the text domain Support for the <slug> placeholder in custom output paths 10 configurable inputs for flexible generation 4 action outputs for use in GitHub Actions workflows Validation and clear GitHub Actions log annotations for improved error reporting 🧪 Quality Comprehensive test suite covering plugins, themes, custom configurations, include/exclude patterns, and source subdirectories CI pipeline with schema validation, ShellCheck, actionlint, and end-to-end tests Dependabot configuration for GitHub Actions and Docker dependencies Conventional Commit enforcement with Commitlint 🚀 Quick Start - name: Generate POT file uses: WPTechnix/wp-pot-generator@v1 See the README for full documentation and configuration examples.

Version updated for https://github.com/y-matsuo081991/ai-adr-enforcer to version v1.1.6. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. What’s Changed Full Changelog: https://github.com/y-matsuo081991/ai-adr-enforcer/compare/v1.1.5...v1.1.6

Version updated for https://github.com/zmaril/housekeeping to version v1.6.0. This action is used across all versions by 3 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Multi-language coverage: ci-exists demands test+lint+fmt per detected language (rust, js, python, ruby, go); ruby joins ecosystem detection; new builds check (every build target runs in CI, tauri heavy-target rules) and codegen-drift check ([[codegen]]-declared regen commands must run + zero-diff in CI). v1 fast-forwarded.

Version updated for https://github.com/Goldziher/polylint to version v0.4.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. What’s Changed Added Colored poly hooks install / uninstall output — a green ✓ header with the hook count and the (relative) hooks directory, then one line per hook name, replacing the flat list of absolute paths. Changed Installed git-hook shims resolve poly from PATH rather than baking in an absolute path to the binary, so a hook always runs whatever poly is current (a recorded absolute path could pin a stale or moved build). When poly is not on PATH the shim now fails with a clear, actionable message and a non-zero exit instead of proceeding as though the hook had passed. Re-run poly hooks install to migrate existing shims. Fixed Native-toolchain formatter output is normalized to LF line endings; some first-party CLIs emit CRLF on Windows, which made output platform-dependent.