Repository navigation
chore(release): 1.3.0 — calendar, tasks, skills, Fast Actions; CI on Node 22 (ODIAA-2338) - #34
Merged
Merged
Conversation
…Node 22 (ODIAA-2338) - Bump package, cli, bridge, mcp and server.json to 1.3.0; lockfile follows. - Move [Unreleased] under 1.3.0 and add the entries that were missing (calendar events ODIAA-2328, tasks ODIAA-2329, deterministic skills ODIAA-2332, the calendarWrite/tasksWrite switches). Move the notes-transcribe entry from 1.2.0, which it wasn't in, to 1.3.0. - release and sign-xpi workflows build on Node 22 instead of Node 20. Co-Authored-By: Claude Opus 5.5 <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
1 participant
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
Prepares release 1.3.0, following docs/RELEASING.md steps 1–4. This PR does not create a tag. Tagging
v1.3.0after merge is what publishes to npm and creates the GitHub Release.releaseandsign-xpiworkflows now build on Node 22 (was Node 20, past end of life).npm-publishwas already on 22.engines.node >= 18is unchanged, and thetest.ymlmatrix stays[20, 22].package.json,cli/,bridge/,mcp/, bothserver.jsonfields, andpackage-lock.json. It's a minor bump because the release adds features.[Unreleased]moves under[1.3.0] — 2026-09-28. I added entries that were missing: calendar events + clash detection (ODIAA-2328), tasks +action-items(ODIAA-2329), deterministic skills (ODIAA-2332), and thecalendarWrite/tasksWriteswitches. The notes-transcribe entry (ODIAA-2331) had been filed under 1.2.0. It isn't in thev1.2.1tag, so I moved it to 1.3.0. The staletb calendarsname is corrected totb calendar list.Signed XPI caveat — decide before tagging
The extension is at 2.4.0, and the new calendar, task and Fast Actions commands need it. ATN hasn't signed 2.4.0 yet: sign-xpi run 36389404535 reports it "queued for ATN's manual review (required for Experiment APIs)".
dist/releases/only has the signed 2.1.0 XPI. If we tag now, the release job attaches signed 2.1.0 plus an unsigned 2.4.0 build, and the CHANGELOG says so. The other option is to wait for ATN approval (re-run sign-xpi) so the release ships a signed 2.4.0.Test plan
npm run test:all: exit 0, every suite 0 failednpm run test:pack-smoke: 10 passed, 0 failed (bins print 1.3.0, MCP answers initialize and lists tools)testworkflow on this PRRollback: docs/RELEASING.md § Rollback (deprecate, or move the
latestdist-tag back to 1.2.1).🤖 Generated with Claude Code