Repository navigation
feat(cli): oclif 5 and Node.js 22+, @norbix.ai/ts 1.3, release fixes - #14
Merged
Merged
Conversation
The lockfile pinned @norbix.ai/ts 1.2.0, which has no makeFilePublic / makeFilePrivate / makeFolderPublic / makeFolderPrivate or stopPushCampaign. `norbix files publish|unpublish` and `norbix push stop` call those, so they would fail at runtime (the tests replace the SDK with a recorder and could not catch it). 1.2.0 also defaulted to *.norbix.dev endpoints, while the CLI assumes the *.norbix.ai defaults; 1.3.0 uses https://api.norbix.ai and https://hub.norbix.ai. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
After #5 merged, docs PRs landed seconds later; the run for an earlier SHA logged "The local branch main is behind the remote one, therefore a new version won't be published". Fetch and reset to origin/<branch> first, as norbix-js's release job does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- typescript 5.9 -> 7.0 (native compiler). TS 7 no longer picks up @types/* automatically, so tsconfig lists "types": ["node"]. The build emits the same 122 files; the packed oclif manifest still has all 112 commands. - @inquirer/prompts 7 -> 8 (confirm / input / password API unchanged here). Note: v8 requires Node >= 20.17. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- @oclif/core 4 -> 5, @oclif/plugin-help 6 -> 7, @oclif/plugin-autocomplete 3 -> 4, @oclif/test 4 -> 5, oclif 4 -> 6, @types/node 22 -> 26. - The oclif 5 packages require Node >= 22, so engines.node is now >=22 (Node 18 and 20 are end-of-life). README and the CI matrix (Node 22/24 on Linux, macOS, Windows) follow; the test suite now runs on every matrix entry. Minimum Node.js is now 22. Users on Node 18/20 keep working with 0.1.x. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 16, 2026
|
🎉 This PR is included in version 0.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
Why the release after #5 didn't publish
#5 was rebase-merged, so its
feat(release): …title never became a commit.mainonly hadchore:/ci:/test:/docs(tasks):commits sincev0.1.0, so semantic-release found "no relevant changes". Trusted publishing works: both runs loggedOIDC token exchange with the npm registry succeeded. The "local branch main is behind the remote one" run started while the docs PRs were landing.This PR has real release-worthy commits and a
feat(cli):title, so it publishes 0.2.0 whether it's squash- or rebase-merged.Commits
fix(deps): require@norbix.ai/ts^1.3.0. The lockfile pinned 1.2.0, which has nomakeFilePublic/makeFolderPublic/makeFilePrivate/makeFolderPrivate/stopPushCampaign.norbix files publish|unpublishandnorbix push stopwould fail at runtime; the tests mock the SDK, so they couldn't catch it. 1.2.0 also defaulted to*.norbix.dev; 1.3.0 uses*.norbix.ai, which the CLI already assumes.ci(release): release from the branch tip. The job fetches and resets toorigin/mainbefore running semantic-release, as norbix-js's does, so a merge landing seconds later doesn't swallow a release.chore(deps): TypeScript 7 and @inquirer/prompts 8 (Dependabot chore(deps): bump typescript from 5.9.3 to 7.0.2 #13, chore(deps): bump @inquirer/prompts from 7.10.1 to 8.7.2 #11). TS 7 no longer loads@types/*implicitly, sotsconfig.jsonlists"types": ["node"]. Build output is the same 122 files.feat(cli): oclif 5 and Node.js 22+ (Dependabot chore(deps): bump oclif from 4.23.28 to 6.0.0 #6, chore(deps): bump @types/node from 22.20.1 to 26.5.1 #7, chore(deps): bump @oclif/core from 4.12.0 to 5.0.0 #8, chore(deps): bump @oclif/test from 4.2.0 to 5.0.0 #9, chore(deps): bump @oclif/plugin-help from 6.2.53 to 7.0.0 #10, chore(deps): bump @oclif/plugin-autocomplete from 3.2.53 to 4.0.0 #12).@oclif/core5, plugin-help 7, plugin-autocomplete 4,@oclif/test5,oclif6 and@types/node26. The oclif 5 packages require Node ≥ 22, soengines.nodeis >=22 (Node 18/20 are EOL). README and the CI matrix (Node 22/24 × Linux/macOS/Windows) are updated.Release
The real
analyzeCommits+generateNotessincev0.1.0give 0.2.0: Features:cli: move to oclif 5 and require Node.js 22+; Bug Fixes:deps: require @norbix.ai/ts ^1.3.0. The Node 22 requirement is stated in the release notes, without aBREAKING CHANGEfooter (that would publish 1.0.0).After merge
Close the Dependabot PRs covered here: #6–#13.
Test plan
--help/db --help/files --help, packed oclif manifest (112 commands incl.files:publish,push:stop),npm audit0npm@10 ciandnpm@11 cipass,npm lscleanhttps://api.norbix.ai@norbix.ai/cli@0.2.0on npm with provenance, tagv0.2.0, GitHub Release🤖 Generated with Claude Code