Skip to content

chore(deps): bump the actions group with 2 updates - #526

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-dddda488bc
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions-dddda488bc

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the actions group with 2 updates: taiki-e/install-action and hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml.

Updates taiki-e/install-action from 2.90.3 to 2.90.5

Release notes

Sourced from taiki-e/install-action's releases.

2.90.5

  • Update mise@latest to 2026.11.8.

  • Update cargo-nextest@latest to 0.9.152.

2.90.4

  • Update yq@latest to 4.54.3.

  • Update vacuum@latest to 0.40.1.

  • Update uv@latest to 0.13.8.

  • Update typos@latest to 1.52.2.

  • Update tombi@latest to 1.11.2.

  • Update syft@latest to 1.57.1.

  • Update rafn@latest to 0.1.7.

  • Update osv-scanner@latest to 2.7.1.

  • Update mise@latest to 2026.11.7.

  • Update knope@latest to 0.24.0.

  • Update kingfisher@latest to 2.18.1.

  • Update kache@latest to 2.1.1.

  • Update grcov@latest to 0.10.8.

  • Update cargo-shear@latest to 1.14.1.

  • Update cargo-cyclonedx@latest to 0.5.10.

  • Update cargo-binstall@latest to 1.27.0.

  • Update cargo-audit@latest to 0.23.0.

  • Update biome@latest to 2.6.7.

Changelog

Sourced from taiki-e/install-action's changelog.

[2.90.5] - 2026-11-15

  • Update mise@latest to 2026.11.8.

  • Update cargo-nextest@latest to 0.9.152.

[2.90.4] - 2026-11-14

  • Update yq@latest to 4.54.3.

  • Update vacuum@latest to 0.40.1.

  • Update uv@latest to 0.13.8.

  • Update typos@latest to 1.52.2.

  • Update tombi@latest to 1.11.2.

  • Update syft@latest to 1.57.1.

  • Update rafn@latest to 0.1.7.

  • Update osv-scanner@latest to 2.7.1.

  • Update mise@latest to 2026.11.7.

  • Update knope@latest to 0.24.0.

  • Update kingfisher@latest to 2.18.1.

  • Update kache@latest to 2.1.1.

  • Update grcov@latest to 0.10.8.

  • Update cargo-shear@latest to 1.14.1.

  • Update cargo-cyclonedx@latest to 0.5.10.

  • Update cargo-binstall@latest to 1.27.0.

  • Update cargo-audit@latest to 0.23.0.

  • Update biome@latest to 2.6.7.

Commits

Updates hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml from 0ebbc93a5bd298cf82ccf95b3897cfe9bf86092e to 7b9f145c2194eb0d46ace82a5a4518db5db38a5e

Changelog

Sourced from hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml's changelog.

== Changelog

=== [Unreleased]

==== Added — the classification registry reads a deed first

  • +load_user_classifications+ now reads +<project_root>/audits/assail-classifications_praxis.deed+ first: a DEED +praxis-deed+ with +:profile assail-classifications+ and one +(classification :file "…" :category <Symbol> :audit "…" :rationale "…")+ clause per audited finding. When the deed exists, the legacy +audits/assail-classifications.a2ml+ and +.panic-attack-classifications.a2ml+ are not read; otherwise they are, with their reader unchanged. Suppression semantics are identical: a finding is suppressed when its location and category match an entry. The name ends +_praxis.deed+ because the standards deed grammar (+deed.abnf+ v2.0.0) dispatches a deed's head on its file name, and a bare +assail-classifications.deed+ matches no pattern.
  • New module +panic_attack::deed+: a minimal reader of the deed grammar (header, form, fields, clauses, every value form, filename dispatch, the +:schema-version+ and identity-field side conditions), with line-numbered errors.

==== Changed — a malformed deed registry is an error

  • +load_user_classifications+ returns +Result<Vec<UserClassification>>+ and +apply_user_classifications+ returns +Result<()>+ (both were infallible). A deed registry that breaks the grammar or the profile (unknown field or clause, a string +:category+, an unknown category, a missing +:file+, the wrong head, trailing content, over 4 MiB, not UTF-8) is an +Err+ naming the file and line, and +analyze()+ / +analyze_verbose()+ fail with it instead of reading it as an empty registry or falling back to the A2ML files. Library callers must handle the +Result+.

==== Changed — the AI manifest reads a deed first; this repo is off A2ML

  • +Manifest::load_default+, +panic-attack manifest+ and +panic-attack diagnostics+ read +0-AI-MANIFEST.deed+ first (a pointer-only +repo-deed+, parsed with +panic_attack::deed+), then the legacy +0-AI-MANIFEST.a2ml+ or +AI.a2ml+ as a read-only fallback. A deed manifest carries no report settings, so it gets the built-in defaults (formats json and nickel, storage filesystem); a legacy manifest's +(reports …)+ is still honoured. A malformed or non-+repo-deed+ deed manifest is an error. New: +MANIFEST_CANDIDATES+, +Manifest::default_path+, +Manifest::path+, +Manifest::is_deed+.
  • +diagnostics+ looks for panicbot directives as the +(bot-directives (bot :name panicbot …))+ clause of the repo deed, not at +.machine_readable/bot_directives/panicbot.scm+; none declared is reported OK (panicbot runs the full suite) rather than as a warning.
  • The repo's own +.a2ml+ files are gone (25 of 26), translated where a

... (truncated)

Commits
  • 7b9f145 fix(assail): blank // comments only where // is a comment (#305)
  • 54da3aa fix(assail): strip proof comments in one pass, blanking in place (#304)
  • f2c46ba fix: Nickel strings stay literal; a manifest lookup error is not an absent ma...
  • c5fc2c6 fix: valid assault-report Nickel, no spurious manifest warning, pointer-only ...
  • e9c8331 fix(manifest): close the review findings left on the deed migration (#298) (#...
  • 656b248 fix(ci): boj-build passes context through env and posts only over https (#299)
  • 6262892 chore(deps): bump ureq from 3.5.0 to 3.5.1 in the rust-minor group (#272)
  • 25ec156 chore(deps): bump the actions group across 1 directory with 4 updates (#284)
  • 29f7b55 Chore/a2ml to deed (#298)
  • 89d4810 deed(identity): carry the registered v8 ids, not #u5 literals (#297)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the actions group with 2 updates: [taiki-e/install-action](https://github.com/taiki-e/install-action) and [hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml](https://github.com/hyperpolymath/panic-attack).


Updates `taiki-e/install-action` from 2.90.3 to 2.90.5
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](taiki-e/install-action@v2.90.3...v2.90.5)

Updates `hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml` from 0ebbc93a5bd298cf82ccf95b3897cfe9bf86092e to 7b9f145c2194eb0d46ace82a5a4518db5db38a5e
- [Release notes](https://github.com/hyperpolymath/panic-attack/releases)
- [Changelog](https://github.com/hyperpolymath/panic-attack/blob/main/CHANGELOG.adoc)
- [Commits](hyperpolymath/panic-attack@0ebbc93...7b9f145)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.90.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: hyperpolymath/panic-attack/.github/workflows/scan-and-report.yml
  dependency-version: 7b9f145c2194eb0d46ace82a5a4518db5db38a5e
  dependency-type: direct:production
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 20, 2026
@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

Ask an organization administrator to verify that this bot has an active assigned CodeRabbit review seat. See the seat-assignment guide. After the seat is confirmed, request a review again.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: aabc394e-7ee0-4a50-9198-9d2c313e9dfd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants