Skip to content

chore: republish plugin-api and update pnpm to 11.13.1#8

Merged
RedStar071 merged 1 commit into
mainfrom
claude/changeset-npm-release-unlk2m
Jul 18, 2026
Merged

chore: republish plugin-api and update pnpm to 11.13.1#8
RedStar071 merged 1 commit into
mainfrom
claude/changeset-npm-release-unlk2m

Conversation

@RedStar071

@RedStar071 RedStar071 commented Jul 17, 2026

Copy link
Copy Markdown
Member

🔗 Linked issue

🧭 Context

The @wolfstar/plugin-api package failed to publish to npm due to an issue with the npm trusted-publishing configuration. This PR republishes the package to ensure it reaches the registry, and updates the pinned pnpm version to 11.13.1 with its integrity hash.

📚 Description

This PR addresses a publishing issue with @wolfstar/plugin-api by:

  1. Adding a changeset to trigger a patch release of @wolfstar/plugin-api
  2. Updating the pnpm package manager version from 11.11.0 to 11.13.1 with the full integrity hash for reproducible builds

The npm trusted-publishing configuration issue that prevented the earlier release has been resolved, allowing this republish to succeed.

Key changes

  • Added changeset for @wolfstar/plugin-api patch release
  • Updated packageManager field in package.json to pnpm 11.13.1 with SHA512 integrity hash

Type of Change

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation change
  • Workflow / CI change

Pre-flight Checklist

  • I have read the Contributing Guidelines
  • My code follows the code style of this project
  • I added a changeset with pnpm changeset

https://claude.ai/code/session_01354X5C7KSz5YhkUj9VJCn9


View with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is enabled.

Confidence Score: 5/5

Safe to merge with minimal risk.

The PR only changes release metadata and the root package manager pin. No functional code paths, security boundaries, or build scripts were changed. The changeset targets the existing @wolfstar/plugin-api package correctly.

No files require special attention.

T-Rex T-Rex Logs

What T-Rex did

  • The toolchain pin was verified against the packageManager pin, as shown in the Toolchain pin confirmation transcript.
  • The changeset status was examined and shows a patch release is scheduled for @wolfstar/plugin-api, according to the Changeset status for patch release transcript.
  • Typecheck, build, and tests for @wolfstar/plugin-api were run and completed with success, as evidenced by the Build and tests for @wolfstar/plugin-api transcript.
  • Publint checks passed and the packed tarball contents match the expected package layout, per the Publish shape and publint validation transcript.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "chore: add release changeset for plugin-..." | Re-trigger Greptile

…publish

The two prior release workflow runs failed to publish @wolfstar/plugin-api
to npm with ERR_PNPM_OTP_NON_INTERACTIVE, a known pnpm bug in the OIDC
trusted-publishing flow fixed in pnpm 11.13.0. Bump packageManager to
pnpm@11.13.1 and add a changeset so the next merge to main produces a
Version Packages PR and publish attempt for the package.
@RedStar071 RedStar071 changed the title Republish plugin-api and update pnpm to 11.13.1 chore: republish plugin-api and update pnpm to 11.13.1 Jul 18, 2026
@RedStar071
RedStar071 merged commit 96a9046 into main Jul 18, 2026
16 checks passed
@RedStar071
RedStar071 deleted the claude/changeset-npm-release-unlk2m branch July 18, 2026 13:42
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.

2 participants