Skip to content

chore(deps): update softprops/action-gh-release digest to efb3536 - #23

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/softprops-action-gh-release-digest
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/softprops-action-gh-release-digest

Conversation

@renovate

@renovate renovate Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
softprops/action-gh-release (changelog) action digest 3d0d988 → efb3536

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

jdh313 added a commit that referenced this pull request Sep 18, 2026
A body naming an agent the target does not register is now the
`agent-reference` construct family, declarable as `body-agent-reference`.
Codex registers no agent role from a plugin package (L-010), so a Codex
body saying `@vault-reader` instructs a dispatch that cannot resolve and
the model confabulates rather than degrades. Nothing reported that: the
six construct families are shapes and none matches a bare `@name`, while
`CLAUDE_ONLY_CONSTRUCTS` was closed, so the loss could not even be
written down.

Matched against data rather than shape. Each `@token` resolves against
the agents the same package declares — frontmatter `name:`, or the
filename stem, the fallback `agent-command.ts` already applies. A
declared name is a collaborator reference and anything else is prose, so
the detector carries no heuristic. That is also why the leading guard
admits `` `@name` ``, `(@name)` and `[@name]`: the dominant spelling in
real corpora is backticked, and widening costs nothing when the match is
keyed on a declaration. The shape-keyed `file-reference` matcher keeps
its path-separator requirement untouched, and the two families stay
disjoint.

Resolution is package-local. A body naming a sibling package's agent is
not detected — Fibery Charting #23 carries that deferred fork.

ndr:c5haze

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
github-actions Bot pushed a commit that referenced this pull request Sep 18, 2026
# [1.0.0](v0.5.0...v1.0.0) (2026-09-18)

* feat(install)!: drop the inert Codex agent project scope ([c725c45](c725c45))

### Bug Fixes

* **capabilities:** correct the hook parity record and cite its source ([d9da868](d9da868))
* **capabilities:** move Codex plugin-root translation to the hook surface ([ca5692c](ca5692c))
* **capabilities:** review followups for ndr:61cmc9 ([2e42a03](2e42a03))

### Features

* **agent:** admit the Claude fields its loader enforces ([4c0c2df](4c0c2df))
* **capabilities:** classify agent constructs on Codex and at leaf scope ([b16eabf](b16eabf))
* **codex-hooks:** locate hook diagnostics at the event's key line ([5b22346](5b22346))
* **compatibility:** detect an unregistrable collaborator reference ([32da2de](32da2de)), closes [#23](#23)
* **install:** refuse cross-target collisions at a shared install destination ([88bc543](88bc543))
* **render:** give leaf body warnings per-occurrence source locations ([f9a2f3a](f9a2f3a))
* **report:** carry source locations on compiler diagnostics ([a709f88](a709f88))

### BREAKING CHANGES

* `install --target codex --scope project` for an agent
now exits 1 instead of writing an unread file.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@renovate
renovate Bot force-pushed the renovate/softprops-action-gh-release-digest branch from f3ce5ae to 5440d8b Compare September 24, 2026 22:24
@renovate
renovate Bot force-pushed the renovate/softprops-action-gh-release-digest branch from 5440d8b to 53b57cf Compare October 1, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants