fix: use changeset publish to enable GitHub release creation

[eli0shin]

Summary

• Replace custom npm publish script with changeset publish command
• Enable automatic GitHub release creation through changesets/action
• Remove scripts/release.sh as it's no longer needed

Problem

The custom release script (scripts/release.sh) used npm publish directly, which doesn't output the "New tag:" format that changesets/action expects. The changesets/action parses this specific output to detect newly published packages and automatically create GitHub releases. Without this output format, GitHub releases were not being created even though packages were successfully published to npm.

Solution

Switched from the custom bash scripts/release.sh to using bunx changeset publish in the version workflow. The changeset publish command:

• Handles the version check internally (won't re-publish existing versions)
• Outputs in the format that changesets/action expects
• Enables automatic GitHub release creation when packages are published

This simplifies the workflow by removing the custom script and leveraging changesets' built-in publishing mechanism that integrates properly with the changesets/action's release creation feature.

Changes

• Updated .github/workflows/version.yml to use bunx changeset publish instead of custom script
• Removed scripts/release.sh since version checking is handled by changeset publish
• Added changeset documenting the fix

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: d584448

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
barkql	Patch

Not sure what this means? Click here to learn what changesets are.

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

[Copilot]

Pull request overview

This PR modernizes the package publishing workflow by replacing a custom npm publish script with the standard changeset publish command. This change enables automatic GitHub release creation, which was previously failing because the custom script didn't output the format expected by changesets/action.

Key Changes:

• Switch from custom bash scripts/release.sh to bunx changeset publish in the version workflow
• Remove the now-redundant scripts/release.sh file
• Add a changeset documenting the fix

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
.github/workflows/version.yml	Updated publish command to use bunx changeset publish instead of custom script
scripts/release.sh	Removed custom release script as version checking is now handled by changeset publish
.changeset/swift-doors-glow.md	Added changeset documentation for this fix

Comments suppressed due to low confidence (1)

.github/workflows/version.yml:41

• The workflow is missing the NPM authentication token required for publishing. When using changeset publish, you need to provide either NODE_AUTH_TOKEN or NPM_TOKEN in the environment variables. Since actions/setup-node@v4 is configured with registry-url, add NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} to the env section alongside GITHUB_TOKEN.

          publish: bunx changeset publish
          title: 'chore: version packages'
          createGithubReleases: true
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

---

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