Conversation
…ut a GUI install. Replaces the manual CONTRIBUTING flow (install vsix in VS Code, then copy ~/.vscode/extensions into the gulp output) with native macOS/Windows/Linux runners, explicit extension clones, optional signing, and draft GitHub Releases. Unsigned artifacts are a first-class path when maintainer secrets are missing. Co-authored-by: Jazii <ItsJazii@users.noreply.github.com>
ItsJazii
marked this pull request as ready for review
September 15, 2026 07:35
ItsJazii
requested review from
a team,
Fryingpannn and
nang-dev
as code owners
September 15, 2026 07:36
Author
|
Update: marked ready for review. Also kicked off a Script self-tests already green on the PR path. Happy to address review comments quickly. |
Expand embed/collect self-tests (win32/darwin, re-embed, error paths, unsigned deb/rpm/setup). Install the editor with npm ci instead of yarn --frozen-lockfile because Yarn 1.22 cannot parse the pre-existing yarn.lock on main. Stop cancelling workflow_dispatch dry-runs when a later PR validate run starts. Co-authored-by: Jazii <ItsJazii@users.noreply.github.com>
Author
|
Follow-up polish pushed to the same branch (
Re-dispatched fork dry-run with the fixed workflow. |
pearai-submodule prepackage downloads a non-zip S3 esbuild archive when GITHUB_ACTIONS is set on ARM. Clear that env so npm esbuild@0.17.19 is used on native arm runners. Roo vsix runs vscode:prepublish -> lint:extension with a Unix env assignment that Windows cmd cannot parse; rewrite the hook to the production compile only. Roo failure is non-fatal so the PearAI vsix still embeds. Co-authored-by: Jazii <ItsJazii@users.noreply.github.com>
Author
|
Follow-up: fixed fork dry-run vsix step ( |
Author
|
Closing — not pursuing; repo appears inactive. |
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
Draft toward #44 (Package Releases Automation).
Hard problem addressed: stop the manual “install
.vsixin a local VS Code/Pear window, then copy~/.vscode/extensions/pearai.pearai-*into the packaged app” step. A.vsixis a zip —scripts/pearai/embed-vsix.shunpacksextension/intoresources/app/extensions/<publisher>.<name>-<version>and removes thepearai-submodulestub.Also includes:
ubuntu-22.04,ubuntu-24.04-arm,macos-13,macos-14,windows-2022(not a fake one-machine-builds-all claim)pearai-submoduleandPearAI-Roo-Code(.gitmoduleswithout gitlink SHAs meanssubmodules: recursiveis a no-op)../VSCode-*+.build/-unsignedartifacts if secrets are missing.github/RELEASE.md+ CONTRIBUTING packaging updatevs competing PRs
publisher.name-versionlayoutsubmodules: recursive(no-op)dist/*.dmgVSCode-*inside repo../VSCode-*+ installersrunstep; unsigned OKFork PR for review history: https://github.com/ItsJazii/pearai-app/pull/1
Test plan
Package & Release → Validate packaging scripts)workflow_dispatchwithdry_run=trueand no secrets — confirmpearai.pearai-*lands underresources/app/extensionsand stub is gone.github/RELEASE.mdand publish draft releaseHappy to iterate on feedback from @nang-dev / maintainers.