Skip to content

chore: release packages - #75

Merged
Ray-56 merged 1 commit into
mainfrom
changeset-release/main
Aug 4, 2026
Merged

chore: release packages#75
Ray-56 merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 4, 2026

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

@call-e/cli@0.3.8

Patch Changes

  • #71 bc70f48 Thanks @EazyHood! - Open the browser without cmd.exe on Windows during auth login.

    cmd /c start "" <url> let cmd parse the OAuth URL, and & is a command separator there, so the URL was truncated at the first & (losing redirect_uri, state and scope) and the rest of the query string was run as shell commands. The opener is now rundll32, which takes the URL as a single argument, named by its fully qualified %SystemRoot%\System32 path so the executable is not resolved through the current working directory.

  • Updated dependencies [566008b]:

    • @call-e/core@0.2.4

@call-e/core@0.2.4

Patch Changes

  • #72 566008b Thanks @EazyHood! - Read numeric token expiries, and refresh instead of caching forever when one cannot be read.

    A broker that sends the expiry as epoch seconds or milliseconds arrived here as a string such as "1700000000000", which new Date() reads as Invalid Date. A valid expiry was therefore indistinguishable from no expiry at all, and the token was cached as if it never expired. Numeric expiries are now parsed explicitly, with values below 1e11 taken as seconds and the rest as milliseconds; a negative or non-finite value is rejected rather than being turned into a nonsense date by new Date("-1").

    An expiry that still cannot be read no longer means "never expires": the entry is treated as expired so the next call refreshes it.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 44a6c07 to 888a9cc Compare August 4, 2026 03:01
@Ray-56
Ray-56 merged commit e5916bf into main Aug 4, 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