v1.1.2: align with vc-vault-factory v0.4.0 + did:stellar

Aligns the SDK (@acta-team/credentials) with the v0.4.0 API (factory + single-tenant vaults) and did:stellar issuance. The SDK is a thin client and the API derives each owner's vault, so the surface changes are focused.

Added

• Issuer deny-list (deny-by-exception; issuance is open by default):
  • client.vaultDenyIssuer(...) for POST /contracts/vault/deny-issuer
  • client.vaultAllowIssuer(...) for POST /contracts/vault/allow-issuer
  • useVault().denyIssuer(...) / allowIssuer(...)
• Optional userSalt on createVault, issue, revoke, and the deny/allow helpers (selects which deterministic vault to target).
• getContractVersion({ owner }) for a per-vault version.
• ConfigResponse now surfaces factoryContractId, networkType, vaultWasmHash, didStellarRegistryId (actaContractId kept as an alias).

Fixed

• useCredential().revoke(...) now sends owner. The v0.4.0 API needs it to derive the single-tenant vault; without it, revocation could not resolve a vault.

Changed

• useVault().authorizeIssuer / revokeIssuer keep working but now map to the API's allow-issuer / deny-issuer aliases. Prefer allowIssuer / denyIssuer.
• Issuance requires a resolvable did:stellar issuer whose controller matches the signer (enforced by the API). useCredential().issue auto-resolves the issuer DID via getOrCreateIssuerIdentity when omitted.

Removed (breaking)

• client.vcIssueLinked and useCredential().issueLinked (linked credentials).
• client.vaultGetVcParent and useVaultRead().getVcParent.

Compatibility

• Requires acta-api v1.1.1.

Verification

• npm run build (tsup ESM/CJS + DTS/typecheck) passes.

v1.1.1

Changelog

All notable changes to @acta-team/credentials are documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

1.1.1 - 2026-05-07

First release under the new package name. Previously published as
@acta-team/acta-sdk,
which is now deprecated.

Migration: replace @acta-team/acta-sdk with @acta-team/credentials in
your package.json. The public hooks (useVault, useVaultRead,
useCredential) and provider (ActaConfig) keep the same names and import
paths.

Highlights

• New package name @acta-team/credentials. The old package is deprecated.
• API alignment with the latest ACTA backend:
  • vcIssue no longer accepts holder. The holder is expressed inside
    vcData (typically credentialSubject.id) following W3C VC 2.0.
  • sourcePublicKey is optional for vault owners that are smart accounts
    (C...) — the backend uses the relayer automatically.
• Linked credentials:
  • New client method vcIssueLinked and hook useCredential().issueLinked
    for POST /contracts/vc/issue-linked.
  • New client method vaultGetVcParent and hook
    useVaultRead().getVcParent for POST /contracts/vault/get-vc-parent.
• Types: added VcIssueLinkedResponse, VaultGetVcParentResponse,
  VaultVcParentInfo.
• CI: the package is now published from GitHub Actions with
  npm provenance.

Breaking changes

• vcIssue({ ..., holder }) is no longer supported. Move the holder into
  vcData (typically credentialSubject.id).

Install

npm install @acta-team/credentials

Links

• npm: https://www.npmjs.com/package/@acta-team/credentials
• Repo: https://github.com/ACTA-Team/acta-credentials