Skip to content

Version Packages - #41

Merged
MyPrototypeWhat merged 1 commit into
mainfrom
changeset-release/main
Oct 26, 2026
Merged

MyPrototypeWhat merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@refkit/core@0.10.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.

@refkit/mcp@0.9.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1
    • @refkit/provider-artic@0.5.1
    • @refkit/provider-gutendex@0.5.1
    • @refkit/provider-internet-archive@0.6.1
    • @refkit/provider-met@0.5.1
    • @refkit/provider-nailbook@0.3.1
    • @refkit/provider-openverse@0.6.1
    • @refkit/provider-poetrydb@0.5.1
    • @refkit/provider-polyhaven@0.5.1
    • @refkit/provider-rijksmuseum@0.5.1
    • @refkit/provider-wikimedia-commons@0.6.1

@refkit/provider-artic@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-brave@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-europeana@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-flickr@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-freesound@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-gutendex@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-internet-archive@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-jamendo@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-met@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-nailbook@0.3.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-openverse@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-pexels@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-pixabay@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-poetrydb@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-polyhaven@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-rijksmuseum@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-smithsonian@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-unsplash@0.5.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-wikimedia-commons@0.6.1

Patch Changes

  • a983747: Published from GitHub Actions through npm trusted publishing (OIDC) instead of a long-lived npm token, so every version now carries a signed provenance statement that links it to the exact commit and workflow run that built it. No code changes.
  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@refkit/provider-testkit@0.1.3

Patch Changes

  • Updated dependencies [a983747]
    • @refkit/core@0.10.1

@MyPrototypeWhat
MyPrototypeWhat merged commit ab0fa9f into main Oct 26, 2026
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.

1 participant