Skip to content

chore: sync Registry Stack identifiers - #6

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/registry-stack-identifiers
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
automation/registry-stack-identifiers

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Summary

Synchronize the active identifier allowlist from Registry Stack commit cedfcdace50460725049e276f3fdea381a8da48e.

This branch is automation-owned. Do not push human edits to it; change Registry Stack source or open a separate publisher PR instead.

registrystack-id@0.1.0 report:catalog
node scripts/report-catalog-change.mjs origin/main

Identifier catalog change

Published identifiers: 76 -> 117

Added (41)

  • https://id.registrystack.org/problems/registry-casework/absence/cover-cycle
  • https://id.registrystack.org/problems/registry-casework/absence/invalid-period
  • https://id.registrystack.org/problems/registry-casework/absence/overlap
  • https://id.registrystack.org/problems/registry-casework/absence/self-cover
  • https://id.registrystack.org/problems/registry-casework/authentication/refused
  • https://id.registrystack.org/problems/registry-casework/clock/recompute-preview-expired
  • https://id.registrystack.org/problems/registry-casework/cursor/expired
  • https://id.registrystack.org/problems/registry-casework/cursor/invalid
  • https://id.registrystack.org/problems/registry-casework/idempotency/expired
  • https://id.registrystack.org/problems/registry-casework/idempotency/key-reused
  • https://id.registrystack.org/problems/registry-casework/operation/not-authorized
  • https://id.registrystack.org/problems/registry-casework/precondition/failed
  • https://id.registrystack.org/problems/registry-casework/precondition/required
  • https://id.registrystack.org/problems/registry-casework/profile/not-authorized
  • https://id.registrystack.org/problems/registry-casework/profile/not-human
  • https://id.registrystack.org/problems/registry-casework/request/body-too-large
  • https://id.registrystack.org/problems/registry-casework/request/invalid
  • https://id.registrystack.org/problems/registry-casework/request/method-not-allowed
  • https://id.registrystack.org/problems/registry-casework/request/not-found
  • https://id.registrystack.org/problems/registry-casework/request/reason-unsupported
  • https://id.registrystack.org/problems/registry-casework/request/source-rejected
  • https://id.registrystack.org/problems/registry-casework/request/unprocessable
  • https://id.registrystack.org/problems/registry-casework/request/unsupported-media-type
  • https://id.registrystack.org/problems/registry-casework/runtime/failure
  • https://id.registrystack.org/problems/registry-casework/service/unavailable
  • https://id.registrystack.org/problems/registry-casework/source-profile/not-applicable
  • https://id.registrystack.org/problems/registry-casework/source-profile/required
  • https://id.registrystack.org/problems/registry-casework/source/bad-gateway
  • https://id.registrystack.org/problems/registry-casework/source/not-found
  • https://id.registrystack.org/problems/registry-casework/source/record-missing
  • https://id.registrystack.org/problems/registry-casework/source/reviewer-not-authorized
  • https://id.registrystack.org/problems/registry-casework/source/signature-invalid
  • https://id.registrystack.org/problems/registry-casework/work-item/already-claimed
  • https://id.registrystack.org/problems/registry-casework/work-item/not-holder
  • https://id.registrystack.org/problems/registry-casework/work-item/not-offered
  • https://id.registrystack.org/problems/registry-casework/work-item/not-visible
  • https://id.registrystack.org/problems/registry-casework/work-item/proposal-changed
  • https://id.registrystack.org/problems/registry-casework/work-item/recovery-pending
  • https://id.registrystack.org/problems/registry-casework/work-item/source-unavailable
  • https://id.registrystack.org/problems/registry-casework/work-item/superseded
  • https://id.registrystack.org/schemas/casework/runtime/runtime.v1alpha1.schema.json

Removed (0)

None.

Metadata updated (4)

  • https://id.registrystack.org/schemas/breg/authoring/registry-module.v1alpha1.schema.json
  • https://id.registrystack.org/schemas/breg/authoring/registry-project.v1alpha1.schema.json
  • https://id.registrystack.org/schemas/breg/runtime/runtime.v1alpha1.schema.json
  • https://id.registrystack.org/vocab/handling

Artifact digest updated (3)

  • https://id.registrystack.org/schemas/breg/authoring/registry-module.v1alpha1.schema.json
  • https://id.registrystack.org/schemas/breg/authoring/registry-project.v1alpha1.schema.json
  • https://id.registrystack.org/schemas/breg/runtime/runtime.v1alpha1.schema.json

Checks

  • npm run check:upstream -- _upstream/registry-stack
  • npm test

All checks ran before this branch was pushed.

@github-actions
github-actions Bot force-pushed the automation/registry-stack-identifiers branch 5 times, most recently from f060230 to 0dd3154 Compare September 15, 2026 12:45
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@github-actions
github-actions Bot force-pushed the automation/registry-stack-identifiers branch from 0dd3154 to 7c57b73 Compare September 16, 2026 12:40
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