Skip to content

chore(release): v1.3.0 - #447

Open
lmars wants to merge 1 commit into
mainfrom
release/v1.3.0
Open

chore(release): v1.3.0#447
lmars wants to merge 1 commit into
mainfrom
release/v1.3.0

Conversation

@lmars

@lmars lmars commented Sep 8, 2026

Copy link
Copy Markdown
Member

Prepares the v1.3.0 release: bumps package.json to 1.3.0 and adds the CHANGELOG entry for everything merged since v1.2.1.

Minor, not patch — this release adds features (local server support, ABLY_URL/--url routing, Ably Chat integration rule types), matching how 1.1.0 and 1.2.0 were cut for feature additions.

What's in it

Local server support (#437)

  • ably accounts login --local stores a locally-running server as an ordinary account profile
  • ABLY_URL / --url set host, port and TLS from a single value for one-off targeting
  • "Using:" banner now names the endpoint whenever it is not Ably's default, and names the plane the command reaches
  • accounts list/switch report endpoint and control plane URLs

Ably Chat integration rules (#433 and predecessors, DX-1546)

  • integrations create supports the chat rule types (http/before-publish, the moderation vendors, aws/lambda/before-publish)
  • --chat-room-filter on create/update, displayed on get/list/delete
  • Several display and validation fixes on integrations update/delete

Security

Validation

  • pnpm prepare — clean
  • pnpm exec eslint src test scripts packages — 0 errors (10 pre-existing warnings)
  • pnpm test:unit — 2644 passed, 1 todo
  • pnpm test:tty — 5 passed

After merge

Tag the merge commit to trigger the release workflow:

git tag -a v1.3.0 -m "Release v1.3.0"
git push origin v1.3.0

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
cli-web-cli Ready Ready Preview Sep 8, 2026 2:16pm UTC

Request Review

@claude-code-ably-assistant

Copy link
Copy Markdown

Walkthrough

This PR prepares the v1.3.0 release by bumping the package version and adding a comprehensive CHANGELOG entry. All the actual feature and bug-fix work was merged in prior PRs (#433, #435, #437 and related); this PR is purely the release bookkeeping step that precedes tagging.

Changes

Area Files Summary
Config package.json Version bumped from 1.2.11.3.0
Docs CHANGELOG.md Added full [1.3.0] entry covering Added/Changed/Fixed across all merged PRs

Review Notes

  • No code changes — this PR contains only version and changelog updates; all feature/fix logic is already on main via previously merged PRs.
  • Minor vs patch: The PR author explicitly notes this is a minor bump (1.3.0 not 1.2.2) because it introduces new features (local server support, ABLY_URL/--url, Chat integration rules). Verify that's the right call for your versioning policy.
  • After merge: Releasing requires a manual tag step (git tag -a v1.3.0 -m "Release v1.3.0" && git push origin v1.3.0) to trigger the release workflow — this is not automated by the merge itself.
  • CHANGELOG accuracy: The entry references docs/Local-Server.md — confirm that file landed in a prior PR and is present on main.
  • tar security bump (7.5.21, fix(deps): bump tar from 7.5.15 to 7.5.21 #435) is listed here but the actual dependency change was in a prior PR; this entry just documents it in the changelog.

🤖 Generated with Claude Code

@claude-code-ably-assistant claude-code-ably-assistant Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: chore(release): v1.3.0

This is a clean, minimal release prep PR — two files changed, no code modifications. The version bump (1.2.1 → 1.3.0) is correctly a minor rather than patch bump given the feature additions (local server support, ABLY_URL, chat integration rules). Semver is right.

One issue to fix before merging:

CHANGELOG: Incorrect vulnerability range for tar

In the Fixed section: Bumped tar to 7.5.21 to cover a vulnerability in the 7.5.11-7.5.21 range.

The range 7.5.11-7.5.21 includes the fixed version itself, implying 7.5.21 is still vulnerable. This should almost certainly be 7.5.11-7.5.20 (the affected versions) fixed by bumping to 7.5.21.

Suggested fix: Bumped tar to 7.5.21 to cover a vulnerability in the 7.5.11-7.5.20 range.

Everything else looks good: changelog format follows Keep a Changelog, date matches the release date, entries accurately describe what is in the included PRs (#437, #433, #435), and the format is consistent with prior release entries.

@claude-code-ably-assistant

Copy link
Copy Markdown

Note: The review above (posted via API) has unformatted text due to sandbox restrictions. Please see the intended formatted version below.

@claude-code-ably-assistant

Copy link
Copy Markdown

Formatted review (re-post):

@claude-code-ably-assistant

Copy link
Copy Markdown

Formatted review content (markdown):

Review: chore(release): v1.3.0

This is a clean, minimal release prep PR. Two files changed, no code modifications. Version bump 1.2.1 to 1.3.0 is correctly minor not patch given feature additions. Semver is right.

Issue: CHANGELOG vulnerability range for tar is wrong. "7.5.11-7.5.21" includes the fix itself. Should be "7.5.11-7.5.20". Fix: change to "in the 7.5.11-7.5.20 range".

Otherwise looks good - Keep a Changelog format, correct date, PRs #437 #433 #435 described correctly.

@lmars
lmars requested a review from umair-ably September 8, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant