Skip to content

Version Packages#263

Merged
yota88 merged 1 commit into
mainfrom
changeset-release/main
Jul 9, 2026
Merged

Version Packages#263
yota88 merged 1 commit into
mainfrom
changeset-release/main

Conversation

@yota88

@yota88 yota88 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by automation. When you're ready to do a release, you can merge this and publish to npm yourself.
If you're not ready to do a release yet, that's fine, whenever you re-run the release script in main, this PR will be updated.

Releases

@palantir/pack.state.core@0.19.0

Minor Changes

  • 9d0c61a: Bump @osdk/foundry.pack to ^2.68.0, surface owningApplicationId on document types, and add document-to-application resolution.

    The SDK adds owningApplicationId to the wire DocumentType, populated from the type's
    metadata. DocumentType (state.core) now carries owningApplicationId?: string and
    FoundryDocumentService maps it through, so it rides along on every
    loadDocumentTypeByName / getDocumentType call.

    Adds resolveDocumentApplication(docRef) to DocumentService (and app.state), backed by
    the new GET /v2/pack/documents/{documentId}/resolveApplication endpoint. Given a document,
    it resolves the owning application id from the document's type metadata, returning undefined
    when none is configured. Unsupported on the in-memory and demo services.

    createDocumentEditDescription no longer sends the deprecated eventData.version or top-level
    eventType fields (both are now optional in the SDK/API and superseded by eventData.schemaVersion
    and eventData.eventType).

    searchDocuments accepts an optional ontologyRid in its options, forwarded to the search
    request to scope results to a specific ontology. Not defaulted — omitted when unset, in which
    case the document type name is searched across all ontologies.

@palantir/pack.state.demo@0.17.0

Minor Changes

  • 9d0c61a: Bump @osdk/foundry.pack to ^2.68.0, surface owningApplicationId on document types, and add document-to-application resolution.

    The SDK adds owningApplicationId to the wire DocumentType, populated from the type's
    metadata. DocumentType (state.core) now carries owningApplicationId?: string and
    FoundryDocumentService maps it through, so it rides along on every
    loadDocumentTypeByName / getDocumentType call.

    Adds resolveDocumentApplication(docRef) to DocumentService (and app.state), backed by
    the new GET /v2/pack/documents/{documentId}/resolveApplication endpoint. Given a document,
    it resolves the owning application id from the document's type metadata, returning undefined
    when none is configured. Unsupported on the in-memory and demo services.

    createDocumentEditDescription no longer sends the deprecated eventData.version or top-level
    eventType fields (both are now optional in the SDK/API and superseded by eventData.schemaVersion
    and eventData.eventType).

    searchDocuments accepts an optional ontologyRid in its options, forwarded to the search
    request to scope results to a specific ontology. Not defaulted — omitted when unset, in which
    case the document type name is searched across all ontologies.

Patch Changes

  • Updated dependencies [9d0c61a]
    • @palantir/pack.state.core@0.19.0

@palantir/pack.state.foundry@0.22.0

Minor Changes

  • 9d0c61a: Bump @osdk/foundry.pack to ^2.68.0, surface owningApplicationId on document types, and add document-to-application resolution.

    The SDK adds owningApplicationId to the wire DocumentType, populated from the type's
    metadata. DocumentType (state.core) now carries owningApplicationId?: string and
    FoundryDocumentService maps it through, so it rides along on every
    loadDocumentTypeByName / getDocumentType call.

    Adds resolveDocumentApplication(docRef) to DocumentService (and app.state), backed by
    the new GET /v2/pack/documents/{documentId}/resolveApplication endpoint. Given a document,
    it resolves the owning application id from the document's type metadata, returning undefined
    when none is configured. Unsupported on the in-memory and demo services.

    createDocumentEditDescription no longer sends the deprecated eventData.version or top-level
    eventType fields (both are now optional in the SDK/API and superseded by eventData.schemaVersion
    and eventData.eventType).

    searchDocuments accepts an optional ontologyRid in its options, forwarded to the search
    request to scope results to a specific ontology. Not defaulted — omitted when unset, in which
    case the document type name is searched across all ontologies.

Patch Changes

  • Updated dependencies [9d0c61a]
    • @palantir/pack.state.core@0.19.0
    • @palantir/pack.state.foundry-event@0.21.0

@palantir/pack.state.foundry-event@0.21.0

Minor Changes

  • 9d0c61a: Bump @osdk/foundry.pack to ^2.68.0, surface owningApplicationId on document types, and add document-to-application resolution.

    The SDK adds owningApplicationId to the wire DocumentType, populated from the type's
    metadata. DocumentType (state.core) now carries owningApplicationId?: string and
    FoundryDocumentService maps it through, so it rides along on every
    loadDocumentTypeByName / getDocumentType call.

    Adds resolveDocumentApplication(docRef) to DocumentService (and app.state), backed by
    the new GET /v2/pack/documents/{documentId}/resolveApplication endpoint. Given a document,
    it resolves the owning application id from the document's type metadata, returning undefined
    when none is configured. Unsupported on the in-memory and demo services.

    createDocumentEditDescription no longer sends the deprecated eventData.version or top-level
    eventType fields (both are now optional in the SDK/API and superseded by eventData.schemaVersion
    and eventData.eventType).

    searchDocuments accepts an optional ontologyRid in its options, forwarded to the search
    request to scope results to a specific ontology. Not defaulted — omitted when unset, in which
    case the document type name is searched across all ontologies.

Patch Changes

  • Updated dependencies [9d0c61a]
    • @palantir/pack.state.core@0.19.0

@palantir/pack.app@0.20.0

Patch Changes

  • Updated dependencies [9d0c61a]
    • @palantir/pack.state.core@0.19.0
    • @palantir/pack.state.foundry@0.22.0
    • @palantir/pack.state.demo@0.17.0

@palantir/pack.state.react@0.20.0

Patch Changes

  • Updated dependencies [9d0c61a]
    • @palantir/pack.state.core@0.19.0

@changelog-app

changelog-app Bot commented Jul 9, 2026

Copy link
Copy Markdown

Generate changelog in packages/app/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Generate changelog in packages/state/core/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Generate changelog in packages/state/demo/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Generate changelog in packages/state/foundry-event/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Generate changelog in packages/state/foundry/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Generate changelog in packages/state/react/changelog/@unreleased

Type (Select exactly one)

  • Feature (Adding new functionality)
  • Improvement (Improving existing functionality)
  • Fix (Fixing an issue with existing functionality)
  • Break (Creating a new major version by breaking public APIs)
  • Deprecation (Removing functionality in a non-breaking way)
  • Migration (Automatically moving data/functionality to a new system)

Description

Version Packages


Check the box to generate changelog(s)

  • Generate changelog entry

@yota88 yota88 force-pushed the changeset-release/main branch from d310e3d to 2d3a796 Compare July 9, 2026 23:24
@changelog-app

changelog-app Bot commented Jul 9, 2026

Copy link
Copy Markdown

Successfully generated changelog entries for:

  • packages/app/changelog
  • packages/state/core/changelog
  • packages/state/demo/changelog
  • packages/state/foundry-event/changelog
  • packages/state/foundry/changelog
  • packages/state/react/changelog

Need to regenerate?

Simply interact with the changelog bot comment again to regenerate these entries.


📋Changelog Preview

💡 Improvements

  • Version Packages (#263)
  • Version Packages (#263)
  • Version Packages (#263)
  • Version Packages (#263)
  • Version Packages (#263)
  • Version Packages (#263)

@yota88 yota88 requested a review from zerovox July 9, 2026 23:28
@yota88 yota88 merged commit 540cb77 into main Jul 9, 2026
15 checks passed
@yota88 yota88 deleted the changeset-release/main branch July 9, 2026 23:57
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.

3 participants