chore: prepare release 1.0.0#380
Open
umair-ably wants to merge 3 commits intomainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughThis PR prepares the first stable major release ( Changes
Review Notes
|
Collaborator
Author
|
waiting for #373 before this can be merged |
sacOO7
reviewed
May 1, 2026
|
|
||
| ## [1.0.0] - 2026-05-01 | ||
|
|
||
| First stable release. This is a large release that overhauls authentication, command argument conventions, output formatting, and adds several new command groups. Key user-facing changes are summarised below; review the migration notes before upgrading. |
Contributor
There was a problem hiding this comment.
Had a question, we didn't include any points from proposed changelog entry at https://ably-real-time.slack.com/archives/C09M25LCZLP/p1777559095294669?thread_ts=1777545682.860959&cid=C09M25LCZLP , is this intentional?
Collaborator
Author
There was a problem hiding this comment.
yeah that's for changelog.ably.com
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.0.0 is the first stable release. Remove the formatReleaseStatus helper and replace its callers in the help banner and interactive welcome with a plain "Version X" line. Drop the now-duplicate version line from `ably version` and `--version` (already covered by formatVersionString). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds a BREAKING entry alongside the other v1.0.0 breaking items and a matching migration step covering the removal of the TOKEN positional in favour of --client-id / --revocation-key. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@ably/cliand@ably/react-web-clifrom0.17.0→1.0.0[1.0.0] - 2026-05-01entry toCHANGELOG.mdsummarising user-facing changes since v0.17.0 (109 PRs, ~457 commits)This is the first stable major release. The CHANGELOG covers OAuth Device Authorization login, the unified
--forceflag for destructive operations, the structured JSON output envelope with status/completed signals, errorhintfields, new command groups (chat mutations, push publish, annotations, expanded spaces, integrations, mutable-message channel rules), the breaking removal of auth flags, the move of primary entity identifiers from--name/--channel/etc. flags to positional arguments, and standardised pagination, time-range flags, and error handling. Migration notes are included.Test plan
pnpm prepare(build + manifest)pnpm generate-docpnpm exec eslint .— 0 errorspnpm test:unit— 2372 passed, 1 todo, 1 skippedv1.0.0on main to triggerrelease.yml(npm publish) andrelease-web-cli.yml