Skip to content

chore(release): v0.17.3 - #186

Merged
SELAT-DEV merged 1 commit into
mainfrom
cursor/release-v0.17.3-2723
Sep 13, 2026
Merged

SELAT-DEV merged 1 commit into
mainfrom
cursor/release-v0.17.3-2723

Conversation

@SELAT-DEV

@SELAT-DEV SELAT-DEV commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

Summary

Patch release so the newly merged selat refund claim|query (#185) can publish to npm. @selat-ai/selat-cli@0.17.2 went out before #185; plugins already pin 0.17.2, so a new version is required before the selat-plugins runtime lock bump.

Changes

  • package.json + bin/selat.mjs VERSION: 0.17.20.17.3 (publish workflow requires these to match)
  • @selat-ai/selat-pay floor: ^0.11.0^0.11.2 (known refund-capable pay; runbook prefers pinning the published floor)
  • package-lock.json refreshed to resolve 0.11.2

No refund behavior changes.

Verification

  • package.json version, bin/selat.mjs VERSION, and selat --version all report 0.17.3
  • npm run check clean
  • npm test: 586/586 pass
  • npm pack --dry-run packs @selat-ai/selat-cli@0.17.3 and includes lib/commands/refund.mjs

After merge

Someone must tag v0.17.3 and push the tag to trigger Trusted Publishing. Do not publish from this PR alone.

Then run selat-plugins' "Sync selat-cli version" workflow_dispatch and merge its marker PR.

Open in Web Open in Cursor 

Publish the merged selat refund claim|query command (#185). Bump package
and bin VERSION together, and raise the selat-pay floor to ^0.11.2 so the
bundled runtime is the known refund-capable pay.

Required before the selat-plugins runtime lock bump. After merge, tag
v0.17.3 and push to trigger Trusted Publishing.

Co-authored-by: SELAT-DEV <SELAT-DEV@users.noreply.github.com>
@SELAT-DEV
SELAT-DEV marked this pull request as ready for review September 13, 2026 03:15
@SELAT-DEV
SELAT-DEV merged commit be30280 into main Sep 13, 2026
1 check passed
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