Update release workflow and package repositories

[codebycarson]

This pull request primarily updates the repository metadata in several package.json files to use the correct multi-package (monorepo) format and makes minor improvements to the release workflow. The changes ensure each package correctly references its location in the monorepo and improve release automation compatibility with npm.

Repository metadata standardization:

• Updated the repository field in the package.json files for @sei-js/create-sei, @sei-js/ledger, @sei-js/precompiles, @sei-js/registry, and @sei-js/sei-global-wallet to use the object format with the correct directory property, ensuring accurate links and improved compatibility with npm and GitHub. [1] [2] [3] [4] [5]
• Fixed the repository field in packages/mcp-server/package.json to point to the correct monorepo URL and directory.

Release workflow improvements:

• Added explicit permissions for id-token, contents, and pull-requests in .github/workflows/release.yml to support secure publishing and automation.
• Configured actions/setup-node with the registry-url for npm publishing in the release workflow.
• Removed unused environment variables (NPM_TOKEN, NX_CLOUD_ACCESS_TOKEN) from the release workflow, likely due to improved authentication methods.Add OIDC permissions and npm registry config to the release workflow, and remove direct NPM_TOKEN/NX_CLOUD_ACCESS_TOKEN env usage. Standardize package.json repository metadata across multiple packages to point to the monorepo (https://github.com/sei-protocol/sei-js.git) with package-specific directory fields.

Files changed: .github/workflows/release.yml, packages/create-sei/package.json, packages/ledger/package.json, packages/mcp-server/package.json, packages/precompiles/package.json, packages/registry/package.json, packages/sei-global-wallet/package.json.

These changes enable tokenless (id-token) publishing flows and make package repo metadata accurate for each package in the monorepo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 099cd16

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.69%. Comparing base (34a09d8) to head (099cd16).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #302   +/-   ##
=======================================
  Coverage   79.69%   79.69%           
=======================================
  Files          83       83           
  Lines        1305     1305           
  Branches      187      215   +28     
=======================================
  Hits         1040     1040           
  Misses        259      259           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

.github/workflows/release.yml:51

• The publish step runs pnpm release (which executes changeset publish), but the workflow no longer provides any npm authentication (no NODE_AUTH_TOKEN/NPM_TOKEN and no .npmrc token setup). Unless npm Trusted Publishing via OIDC is already configured for these packages, this will cause npm publishes to fail (typically with an auth error). Add the appropriate npm auth mechanism (e.g., set NODE_AUTH_TOKEN for this step, or add the required config/flags for OIDC trusted publishing).

          # Release builds the packages and calls changeset publish
          publish: pnpm release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This PR’s description focuses on repository metadata and release workflow changes, but this hunk also changes the author field. If this isn’t intentional, it should be reverted; if it is intentional, please update the PR description to reflect the metadata change (and ensure it matches the desired npm package ownership/attribution).