chore(deps): bump the actions-deps group across 1 directory with 2 updates#5
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps): bump the actions-deps group across 1 directory with 2 updates#5dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
…dates Bumps the actions-deps group with 2 updates in the / directory: [step-security/harden-runner](https://github.com/step-security/harden-runner) and [actions/checkout](https://github.com/actions/checkout). Updates `step-security/harden-runner` from 2.15.1 to 2.19.4 - [Release notes](https://github.com/step-security/harden-runner/releases) - [Commits](step-security/harden-runner@58077d3...9af89fc) Updates `actions/checkout` from 6.0.2 to 6.0.3 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...df4cb1c) --- updated-dependencies: - dependency-name: step-security/harden-runner dependency-version: 2.19.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions-deps - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions-deps ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
goozang-records
added a commit
to goozang-records/canton-token-template
that referenced
this pull request
Jun 7, 2026
…de-review OpenZeppelin#5–#8) Quality/altitude follow-ups from the code review, root-caused rather than patched. OpenZeppelin#5 (altitude) + #7 (DRY): pause and freeze are both origination controls checked at the same chokepoints, so they are unified into a single `assertCanOriginate this <parties>` call at every origination chokepoint (the five factory entry points + direct mint). A new origination path now makes one call covering BOTH gates — it cannot enable one and silently forget the other. The V2 account→parties extraction (owner + provider, addressing the earlier provider gap) is factored into `accountsFreezeParties`, so the resolution rule lives in one place instead of being respelled at each V2 site. (There is no single on-ledger funnel to host the check — the V2 transfer/settlement paths delegate input-archiving to the token-standard library — so the obligation is documented on `assertCanOriginate` and kept to one uniform call.) #8 (type-safety): `assertAccountsNotFrozen` now takes the `SimpleTokenRules` record (reads `.frozenAccounts` itself) instead of a bare `[Party]` first arg, so a call site cannot pass two same-typed party lists in the wrong order — it is type-impossible to swap. OpenZeppelin#6 (consistency): `Rules_FreezeAccount` + `Rules_UnfreezeAccount` collapse into one `Rules_SetAccountFrozen` with a `frozen : Bool`, mirroring `Rules_SetPaused` — the capability gate, admin carve-out, and recreate live once. The two redundancy errors collapse into `eRedundantFreezeChange` (the OZ Pausable non-idempotency, mirroring `eRedundantPauseChange`); the state-must-change guard keeps the set duplicate-free without a separate membership check. Test helpers keep their `freezeAccount`/`unfreezeAccount` names (call sites unchanged). Suite 158/158 green; daml-lint back to the 7-baseline unbounded-fields (a transient false-positive `unguarded-division` on a `/` in a doc comment was removed by rewording). PLAN.md row left unstaged (still contended with the parallel AL-8 doc edit). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
goozang-records
added a commit
to goozang-records/canton-token-template
that referenced
this pull request
Jun 7, 2026
…ed state AL-10 row + §17.5 row 2a now reflect the delivered + code-reviewed AL-10: - `Rules_SetAccountFrozen` (Bool freeze/unfreeze, mirroring `Rules_SetPaused`) replaces the earlier `Rules_FreezeAccount`/`Rules_UnfreezeAccount` pair; - pause + freeze unified into one `assertCanOriginate` gate at every origination chokepoint + direct mint + cold-path mint accept (`Rules_AcceptMintProposal`); - V2 guards check `accountParties` (owner AND provider); - suite 146→158; review fixes #1–#8 landed in c2e61f3 / f062f16. Also carries the parallel AL-8 verify/props status lines (top status block + the AL-8 roadmap row → ✅, daml-verify OpenZeppelin#5 / daml-props #3) that were already staged in the working tree by the concurrent AL-8 effort — included here to land PLAN.md in a consistent state rather than splitting one file across two authors' commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
goozang-records
added a commit
to goozang-records/canton-token-template
that referenced
this pull request
Jun 7, 2026
Code-review follow-ups on the AL-11 seizure (none required design input; the three that do are documented as open design calls). #1 Separation of duties: two-person control only checked `approver /= proposer`, not that the BENEFICIARY differs from the officers — an approver could approve a seizure into their own account. Added `newOwner /= proposer` at propose and `newOwner /= approver && /= proposer` at approve (`eSeizureBeneficiaryIsOfficer`). OpenZeppelin#4 Dead code / phantom doc: `Admin_ProposeSeizure`'s comment promised an approval-time tamper check via `eSeizureHoldingMismatch` that never existed and never ran, and `seizedOwner` was written-never-read. Reworded the comment (cid immutability already forces a re-propose on a stale target) and relabelled `seizedOwner` as audit-only. #8 Dedup: `TransferPreapproval_ReceiveSeized` was byte-for-byte `MintInto`. Factor a shared `createViaPreapproval` body; the two remain distinct CHOICES (for the reconciler's mint-vs-reallocation distinction) but share one implementation. #2/#3 Docs: documented that `ReceiveSeized` is a root-callable create whose supply-neutrality is a caller property (the off-ledger D2 reconciler must net the seizure pair and must not treat a standalone ReceiveSeized as value-neutral), in ADMIN-LAYER-PLAN §11.4. #7/#10 Tests: added test_seizeBeneficiaryCannotBeOfficer, ...ForeignHoldingRejected (cross-registry), ...ForeignPreapprovalRejected (the preapproval.admin guard half), ...ScopedLegalAdmin (instrument-scoped cap, both directions); strengthened the stale-target test to assert no recovery holding was created. Suite 166 -> 170. OpenZeppelin#5/OpenZeppelin#6/#9 design calls recorded as TT-Q-011a/b/c (PLAN §17.7): locked-fund seizure, structural-vs-convention two-person control, court-order onboarding — with recommendations, for your decision (not blockers). daml-lint baseline-clean; 170/170 green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the actions-deps group with 2 updates in the / directory: step-security/harden-runner and actions/checkout.
Updates
step-security/harden-runnerfrom 2.15.1 to 2.19.4Release notes
Sourced from step-security/harden-runner's releases.
... (truncated)
Commits
9af89fcMerge pull request #667 from step-security/update-agent-v1.8.6485dce8Update agent to v1.8.6ab7a940Merge pull request #665 from step-security/fix/use-policy-store-default-auditec41b78Default to audit mode when api-key missing with use-policy-store9ca718dMerge pull request #664 from step-security/update-agent-v1.8.51dee3dfUpdate agent to v1.8.5a5ad31dMerge pull request #657 from devantler/fix/ubuntu-slim-user-env6e92856build dist and trim ubuntu-slim message4e0504eMerge branch 'main' into fix/ubuntu-slim-user-env8d3c67dRelease v2.19.0 (#661)Updates
actions/checkoutfrom 6.0.2 to 6.0.3Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
df4cb1cUpdate changelog for v6.0.3 (#2446)1cce339Fix checkout init for SHA-256 repositories (#2439)900f221fix: expand merge commit SHA regex and add SHA-256 test cases (#2414)0c366fdUpdate changelog (#2357)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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